...hallelujah!
What is Ninject?! (taken from here)
"In 5 seconds
Ninject is the ninja of dependency injectors.
In 30 Seconds
Ninject is a lightning-fast, ultra-lightweight dependency injector 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. "
One of my main bug bears with Spring.NET is the feature bloat (I really don't need 70% of the features) and the xml configuration hell (and the same can be said of many IoC/DI frameworks).
I'm using Castle/Windsor at the moment and even with this lighter weight framework the configuration bogs you down. I have my own solution using "Assemblers" to construct preset object tree implementations of interfaces - the "assemblers" themselves are created using IoC so I can swap out stuff still just not at a fine grained level. However brainer people than I have been attacking this problem and I've run across Ninject and Binsor, plus I've also given myself an idea for a tool - a UI to configure any IoC framework (using schema plugins)...
Anyway back to Ninject....sounds great, can't wait to try it out!
What is Ninject?! (taken from here)
"In 5 seconds
Ninject is the ninja of dependency injectors.
In 30 Seconds
Ninject is a lightning-fast, ultra-lightweight dependency injector 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. "
One of my main bug bears with Spring.NET is the feature bloat (I really don't need 70% of the features) and the xml configuration hell (and the same can be said of many IoC/DI frameworks).
I'm using Castle/Windsor at the moment and even with this lighter weight framework the configuration bogs you down. I have my own solution using "Assemblers" to construct preset object tree implementations of interfaces - the "assemblers" themselves are created using IoC so I can swap out stuff still just not at a fine grained level. However brainer people than I have been attacking this problem and I've run across Ninject and Binsor, plus I've also given myself an idea for a tool - a UI to configure any IoC framework (using schema plugins)...
Anyway back to Ninject....sounds great, can't wait to try it out!
Comments