DI IoC

After having deal with popular IoC container for .NET Ninject  I was wandered about alternatives.

And I found two more:

 

1. Windsor - "Castle Windsor aggregates the MicroKernel and exposes a powerful configuration support. It is suitable for common enterprise application needs. It is able to register facilities and components based on the configuration and adds support for interceptors.".

Looks like most popular.

 

2. autofac - "Autofac was designed with modern .NET features and obsessive object-orientation in mind. It will change the way you approach dependency injection in .NET.".

Young but powerfull proiject.

 

 

igorz 08/11/2009 - 13:26

In yesterday session "What's new in CLR 4.0" Microsoft guys presented new Managed Extensibility Framework.

Which is going to be a part of .NET 4.0.

 

"Application requirements change frequently and software is constantly evolving. As a result, such applications often become monolithic making it difficult to add new functionality. The Managed Extensibility Framework (MEF) is a new library in .NET Framework 4.0 that addresses this problem by simplifying the design of extensible applications and components."

 

Of course they introduce it as totally new apporoach to development and architecture, but in my opinion it is yet another dependency injection framework.

 

In any case it is nice to see it as builtin part of .NET 4.0.

 

Welcome to MEF!.

igorz 19/11/2009 - 10:21

 For all of you tired of creating cumbersome ASP.Net providers and struggling with App.config, a lightweight yet powerful dependency injection for .Net: Ninject. This is an example how the injection works with properties:

 

andrew 02/09/2009 - 14:51
Syndicate content