Last time I looked at either of them I found Ninject slightly better. But both have their drawbacks. Ninject has a better fluent-configuration scheme. Unity seems to rely mostly on XML configuration. Ninject’s main drawback is that it requires you to reference Ninject.Core everywhere in your code to add [Inject] attributes. If I may ask, … Read more
What’s happening is that you’re bitten by this problem. Basically, what happened is that you didn’t register your controllers explicitly in your container. Unity tries to resolve unregistered concrete types for you, but because it can’t resolve it (caused by an error in your configuration), it return null. It is forced to return null, because … Read more
I am preparing a presentation for a usergroup. As such I just went through a bunch of them. Namely: AutoFac, MEF, Ninject, Spring.Net, StructureMap, Unity, and Windsor. I wanted to show off the 90% case (constructor injection, which is mainly what people use an IOC for anyway). You can check out the solution here (VS2008) … Read more
Any place where you need a run-time value to construct a particular dependency, Abstract Factory is the solution. Having Initialize methods on the interfaces smells of a Leaky Abstraction. In your case I would say that you should model the IMyIntf interface on how you need to use it – not how you intent to … Read more
Unity is just an IoC “container”. Google StructureMap and try it out instead. A bit easier to grok, I think, when the IoC stuff is new to you. Basically, if you understand IoC then you understand that what you’re doing is inverting the control for when an object gets created. Without IoC: public class MyClass … Read more
While a comprehensive answer to this question takes up hundreds of pages of my book, here’s a quick comparison chart that I’m still working on: