Microsoft | patterns & practices | Developer Network | Enterprise Library | Acceptance Testing Guide | Personal Site
Friends! Today we have released the February 2008 Community Technology Preview of Unity, our lightweight extensible dependency injection container (it's truly lightweight - to use it, you only need to include 2 assemblies totalling about 100K). Get it from Codeplex: http://www.codeplex.com/unity. It comes with all source, test cases, a couple of examples/quickstarts and an initial set of docs. We look forward to your feedback. Don’t wait for too long. Our final release is on March 15.
Also, as a reminder, registration for the Unity Extensibility Workshop closes on February 15. Your participation is invited. If you want to jam with the Unity authors and other developers who are interested in building extensions for Unity, this is a great opportunity.
PingBack from http://www.biosensorab.org/2008/02/12/unity-february-2008-community-technology-preview/
Sweet! Very cool . Another new toy to try out.
Well it’s a week of news; Scott Guthrie has posted an update on the ASP.NET MVC Framework roadmap , and
I saw only source code of Unity in this CTP release on CodePlex. Where are test cases, a couple of examples/quickstarts and an initial set of docs?
All are in the appropriate folders inside the zip file.
Here is a quickstrart, a small example of Unity. http://geekswithblogs.net/claeyskurt/archive/2008/02/18/119739.aspx
As many people who read this would know, I'm a big fan of IoC containers, more in particular Castle Windsor
Looks like microsofts move towards application server ...which would be a nice to have for enterprise class application
Hmm. I thought the pattern & practices team already had a dependency injection framework called the ObjectBuilder?
I cannot see the differences between OB and the UnityContainer..maybe you can enlighten me?
I used the ObjectBuilder to build business services (WCF) much the same way with a config file telling how to map a specific interface to a concrete class and actual injection (or point of injection) is defined with attributes.
Thought I would share a real world example of where DI can be applied:
Apart for the "normal" use cases as logging, security, etc. I also used DI for business workflows.
The same WCF services are handling many different consumers in the same business segment (travel business). A consumer is considered a different travel agent. But some of these agents have slightly different business workflows for example in respect to price calculation.
I found DI a very neat way to plug-in a new price calculation based on who the consumer is.