-
as seen on Stack Overflow
- Search for 'Stack Overflow'
I'm trying to understand when I should use a container versus manually injecting dependencies. If I have an application that uses a 1-2 interfaces and only has 1-2 concrete implementations for each interface, I would lean towards just handling that myself.
If I have a small application that uses…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
What's the simplest IOC container for C#? Is simple to learn and get productive with for a small app. In my case a winforms app which I want to abstract the data layer for later potential migration to a web-service for the data layer.
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
How should the configuration for an IoC container be organized? I know that registering by code should be placed at the highest level in an application, but what if an application had hundreds of dependencies that need to be registered? Same with XML configurations. I know that you can split up…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
For the purpose of this discussion, there are two kinds of parameters an object constructor might take: state dependency or service dependency. Supplying a service dependency with an IOC container is easy: DI takes over. But in contrast, state dependencies are usually only known to the client. …
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
I've been using Dependency Injection (DI) for awhile, injecting either in a constructor, property, or method. I've never felt a need to use an Inversion of Control (IoC) container. However, the more I read, the more pressure I feel from the community to use an IoC container.
I played with .NET…
>>> More
