In this interview with Nate Kohari, creator of the Ninject dependency injection container for .NET, talks about the release of version 1.0 of Ninject. The interview has taken place over the past weeks leading up to the release of Ninject 1.0.
Nate goes into detail why Ninject was created, its capabilities, how it's different then the competition and much more. Ninject supports the following platforms:
- .NET Framework 2.0, 3.0 and 3.5
- .NET Compact Framework 2.0 and 3.5 (Ninject.Core and Ninject.Conditions)
- Silverlight 2.0 beta 2 (Ninject.Core, Ninject.Conditions, and all shipping extensions)
Features of Ninject 1.0 include:
- Constructor, property, method, and field injection
- Instantiation behaviors (singleton, one-per-thread, one-per-request)
- Fluent interface for declaring type bindings
- Contextual bindings, where the selection of which type to instantiate can be delayed until activation
- Support for instance scope and deterministic disposal
- Fully pluggable, modular design: each kernel component can be easily replaced to alter the framework’s behavior
- Lightweight interceptor support (aspect-oriented programming)
- Integrations with other popular frameworks
Please check out the complete interview Nate Kohari on Releasing Ninject 1.0.
Community comments
Congratulations Nate
by Al Tenhundfeld /
Congratulations Nate
by Al Tenhundfeld /
Your message is awaiting moderation. Thank you for participating in the discussion.
I've experimented with Ninject a little, and it feels much more intuitive to use than the other frameworks I've tested (Spring.NET & Windsor). I think Ninject is a major new contender in the DI/IOC arena, and if it's not attractive enough to pull people away from the other established DI frameworks, it should at least be enough to push the other vendors towards higher usability.