Unity February 2008 Community Technology Preview

Comments

# BioSensorAB » Unity February 2008 Community Technology Preview said on February 12, 2008 7:24 PM:

PingBack from http://www.biosensorab.org/2008/02/12/unity-february-2008-community-technology-preview/

# MichaelD!'s Tech Blog said on February 13, 2008 9:15 PM:

Sweet! Very cool . Another new toy to try out.

# Simon Ince's Blog said on February 14, 2008 4:55 AM:

Well it’s a week of news; Scott Guthrie has posted an update on the ASP.NET MVC Framework roadmap , and

# Noticias externas said on February 14, 2008 5:50 AM:

Well it’s a week of news; Scott Guthrie has posted an update on the ASP.NET MVC Framework roadmap , and

# Tiendq said on February 15, 2008 2:36 AM:

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?

Thanks,

# gmelnik said on February 15, 2008 9:01 AM:

@Tiendq

All are in the appropriate folders inside the zip file.

# kurt said on February 18, 2008 3:10 PM:

Here is a quickstrart, a small example of Unity. http://geekswithblogs.net/claeyskurt/archive/2008/02/18/119739.aspx

# Matthew Podwysocki's Blog said on February 18, 2008 7:48 PM:

As many people who read this would know, I'm a big fan of IoC containers, more in particular Castle Windsor

# Matthew Podwysocki's Blog said on February 18, 2008 7:50 PM:

As many people who read this would know, I'm a big fan of IoC containers, more in particular Castle Windsor

# ashishkad said on February 20, 2008 12:01 AM:

Looks like microsofts move towards application server ...which would be a nice to have for enterprise class application

# hgsdc said on February 26, 2008 5:39 AM:

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.