Note: This post was edited on 21st December 2011, after the first comment was left by Remo Gloor .Using Ninject in a classic DI scenario, means that only the entry point of you code should have knowledge about Ninject. This is different than using it as a Service Locator, where either all classes know about the IoC Container (Ninject, in this case) and access it, meaning that every class is implicitly coupled with it. or, you have to pass the Service Locator as an argument to every class's constructor, ......

Well, after reading the following article, I figured the case Paul Hiles makes is not bad. Not every one wants or needs DI, and granted, in many cases moving from a "IoC Container used as a Service Locator" solution to a "real dependency injection" solution might just be not worth it, I believe that it's a better structure, especially if you're writing from scratch. http://www.devtrends.co.uk/... I'm not writing from scratch, and ......