I do not believe this is possible due to erasure. We generally switched to strongly typed sub-interfaces when going for full-autowiring: public interface LongService extends ISimpleService<Long> {} public interface StringService extends ISimpleService<String> {} Upon doing this switch we found we actually liked this pretty well, because it allows us to do “find usage” tracking much … Read more
Well I ended up redesigning this after reading the book Dependency Injection in .Net (I highly recommend this book to any object-oriented developer, not just .Net developers and not just those interested in using an IoC container!). I’ve now got the following in a Domain assembly: public interface IImageFileService { void RenameFiles(); void CopyFiles(); } … Read more
According to Dependency Injection Principles, Practices and Patterns, a DI Container is: “a software library that provides DI functionality and allows automating many of the tasks involved in Object Composition, Interception, and Lifetime Management. DI Containers are also known as Inversion of Control (IoC) Containers.” (§3.2.2) At the very least, a DI Container allows Auto-Wiring, … Read more
Imagine you are writing library code to be used by 3rd party developers. Your code needs to be able to create service objects that these developers provide. However you don’t know which IoC container each of your callers will be using. The Common Service Locator lets you cope with the above without forcing a given … Read more
I don’t know NInject, but unless it works vastly different than Windsor, StructureMap etc. the answers tend to stay the same, as there are some common DI patterns. With that in mind: The first thing to realize is that DI isn’t tied to a particular framework such as NInject or Windsor. It is a set … Read more
I wrote the code from the top of my head, so there could be a typo or two. You do it just the same as when injecting stuff into activities. Declare a component, add the inject method to that component, add a module providing your service create that components builder add your module to the … Read more
Having recently spiked the use of 6 of these (Windsor, Unity, Spring.Net, Autofac, Ninject, StructureMap) I can offer a quick summary of each, our selection criteria and our final choice. Note: we did not look at PicoContainer.Net as one of our team considered the .Net port to be quite poor from the Java version. We … Read more
The best I can do is to layout the facts as they currently stand. NOTE: A lot has changed since I first answered this in 2017. The information below has continued to be updated and should help you as you look to make decisions on your projects. Do take note however that you do also … Read more
It is very easy using V3.0.0 Bind<I1, I2, I3>().To<Impl>().InSingletonScope();
In common usage, the terms have become somewhat synonymous. The original idea of IoC — Inversion of Control — was very much related to the “Hollywood Principle:” Don’t Call Us, We’ll Call You. In traditional applications, developers would write business code and framework code. The business code would then call the framework code to accomplish … Read more