-
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
-
as seen on Programmers
- Search for 'Programmers'
On the Wikipedia page on dependency injection, the disadvantages section tells us this:
Dependency injection increases coupling by requiring the user of a subsystem to provide for the needs of that subsystem.
with a link to an article against dependency injection.
Dependency injection makes…
>>> More
-
as seen on Gooder Code
- Search for 'Gooder Code'
It’s no secret I am a fan of dependency injection. So I was happy to hear that Dick Wall of the Java Posse recently released a dependency injection framework for scala. Called SubCut, or Scala Uniquely Bound Classes Under Traits, the project is a ‘mix of service locator and dependency…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
I find that my constructors are starting to look like this:
public MyClass(Container con, SomeClass1 obj1, SomeClass2, obj2.... )
with ever increasing parameter list. Since "Container" is my dependency injection container, why can't I just do this:
public MyClass(Container con)
for every class…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
Can anyone point me towards some good documentation / code examples on how best to manage the configuration of a DI container in a scenario where you need different configuations sets?
We have a layered, distributed application that has multiple entry points (ie; a website, winforms app, office plugin…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
I'm trying to introduce DI as a pattern here at work and one of our lead developers would like to know: What - if any - are the downsides to using the Dependency Injection pattern?
Note I'm looking here for an - if possible - exhaustive list, not a subjective discussion on the topic.
>>> More
