Ninject is a lightweight dependency injection framework for .NET applications. It helps you split your application into a collection of loosely-coupled, highly-cohesive pieces, and then glue them back together in a flexible manner. By using Ninject to support your software’s architecture, your code will become easier to write, reuse, test, and modify.
Note: This wiki/site is for the main version of Ninject, which is a ground-up rewrite of Ninject 1. The implementation relies heavily on LINQ, so if you’re not targeting the .NET Framework 3.5 or higher (or equivalent Silverlight/Compact/Mono versions), you’ll need to use version 1 of Ninject.
Continue reading: Why use Ninject?
If you’re very familiar with, or relying on materials targeting v1, you’ll want to read changes in Ninject 2.
Ninject v3 was released in early 2012. To learn more read changes in Ninject 3
Some of the documentation has not yet been synced with the v2 rewrite – see the status overview in the TOC. Please bear with us as the contributors tasked with the work get around to providing detailed and accurate documentation that strikes that critical balance between facts and tutorial. And remember, it’s a wiki – if something confuses you or you feel you can clarify something, don’t hesitate to edit – the worst that can happen is that it’ll be rolled back!
Mastering Ninject for Dependency Injection, by Daniel Baharestani, [PACKT] publishing, 2013.
Licensed under Apache 2 License - Copyright by Ninject Project Contributors
Last edited by Daniel Baharestani,