I’ve used StructureMap quite a bit. The rest of your question is pretty loaded. I’ll try to explain the concept in an example. Suppose you created a website that will accept payments through PayPal. PayPal is now a dependency. But you don’t want to code against a specific PayPal provider. Instead, you would create and … Read more
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
I just blogged about this with a solution. In a nutshell, this solution involves a simple, reusable MembershipProvider that calls the container to resolve your custom MembershipProviders. Unlike other solutions that use “BuildUp” container features, this one takes true control of instantiation, thus enabling constructor injection (which in turn enables immutability) and proxyability.
You have to use conditional bindings e.g Bind<IRepository>().To<Repository>().WhenInjectedInto<CachedRopsitory>(); Bind<IRepository>().To<CachedRepository>().WhenInjectedInto<CachedLoggedRepository>(); Bind<IRepository>().To<CachedLoggedRepository>();
I think you’re basically on the right track – If you have not already I would suggest taking a look at Rhino Igloo, an WebForms MVC framework, Here’s a good blog post on this and the source is here – Ayende (the Author of Rhino Igloo) tackles the issue of using Windsor with webforms quite … Read more
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
It is very easy using V3.0.0 Bind<I1, I2, I3>().To<Impl>().InSingletonScope();
Just for others (like me) who might have faced the above error. The solution in simple terms. You might have missed to register your Interface and class (which implements that inteface) registration in your code. e.g if the error is “The current type, xyznamespace. Imyinterfacename, is an interface and cannot be constructed. Are you missing … Read more
The principle purpose of MEF is extensibility; to serve as a ‘plug-in’ framework for when the author of the application and the author of the plug-in (extension) are different and have no particular knowledge of each other beyond a published interface (contract) library. Another problem space MEF addresses that’s different from the usual IoC suspects, … Read more
A couple of observations: Don’t inject dependencies just to query them in the constructor There’s no reason to inject an ITimeProvider into a user just to invoke Now immediately. Just inject the creation time directly instead: public User(DateTime creationTime) { this.CreationTime = creationTime; } A really good rule of thumb related to DI is that … Read more