69
Vote

Support for the new Unity Dependency Injection Container

description

The Enterprise Library team is switching to use the Unity Dependency Injection Container for their 4.0 release. I think a plan to support the new version should be considered.
 
EntLib V4 Product Backlog: http://www.codeplex.com/entlib/Wiki/View.aspx?title=EntLib4%20Backlog
Unity Dependency Injection Container: http://www.codeplex.com/unity

comments

RouteCoder wrote Jun 3, 2008 at 3:38 PM

I concurr..There is a lot of anxiety around the current dependency injection that it is really slow. Using Unity might address those performance issues.

pbolduc wrote Jun 5, 2008 at 5:36 AM

In Michael Puleio's latest article on 'Converting the Composite Web Application Block to Unity', he comments that number of lines of code went from 26K (pre-article one) to 14K. That is a lot of code!

cdchris wrote Oct 8, 2008 at 3:31 PM

Agreed. For Microsoft's Unity to really have a chance to stand against Castle Windsor, Spring, StructureMap, Ninject it needs to be integrated into WCSF and replace ObjectBuilder/CompositeWeb. Having 2 different DI frameworks will only hurt the adoption of Unity and switching WCSF to use Unity I believe would greatly enhance the robustness of WCSF from the power that the Unity framework leverages.

pbolduc wrote Oct 28, 2008 at 11:00 PM

I remember reading at subtle hint a while back in a WCSF discussion forum post from one of the WCSF project people that we might expect a new version (if we could wait long enough). Well, today Ent Lib 4.1 and Unity 1.2 were released! Any connection with PDC? :-) I'm hoping that this work item is on the team's current pipeline and was waiting for these other releases. Trick or Treat? :-)

Sign in to add a comment or to set email notifications