Ninject is a very good DI framework based on strongly typed binding that facilitates full intellisense DI solution for an app. One of the prominent characteristics, it is fast. But believe me or not, today I found the case that you shouldn't use Ninject or other strong type DI framework. This reminds me, there is no one size fits all DI solution. My project relies on custom build event command line for In-Memory test, NHibernate, and WCF config, each copies its own needed assembly into target bin folder. When the dependencies of these assemblies are dynamic. You can't use strong-typed DI framework with this scenario. One solution I can think of is to use Reflection and invoke methods of dynamic assemblies for using for injection. But this solution is very bad, the code gets too complex and it wasn't worth trying. I get stuck and come back to the old config-based UI framework like Spring.NET :(