As you have already figured out, Dependency Injection (DI) itself is only a collection of patterns and techniques. At the root of the application we wire up all necessary object graphs. This place is called the Composition Root, and we can use a DI Container to do this wiring for us, or we can do … Read more
You have to use conditional bindings e.g Bind<IRepository>().To<Repository>().WhenInjectedInto<CachedRopsitory>(); Bind<IRepository>().To<CachedRepository>().WhenInjectedInto<CachedLoggedRepository>(); Bind<IRepository>().To<CachedLoggedRepository>();
There are certainly people who think that DI Containers add no benefit, and the question is valid. If you look at it purely from an object composition angle, the benefit of a container may seem negligible. Any third party can connect loosely coupled components. However, once you move beyond toy scenarios you should realize that … Read more
When boiled down, the main difference is that IoC containers are generally most useful with static dependencies (known at compile-time), and MEF is generally most useful with dynamic dependencies (known only at run-time). As such, they are both composition engines, but the emphasis is very different for each pattern. Design decisions thus vary wildly, as … Read more
What is it? I think the definition in your answer covers this question well. Although, I question why the definition includes that a component needs to explicitly define its dependencies. A canonical example of a component is an ActiveX control – do they need to explicitly define their dependencies? What problems does it solve? Management … Read more