Skip to main content

Unity Explained

I had some time in the night to make use of the MS Unity applcation block, and I thought of writting a post on an example written uing Unity.
To use the dependency injection in your code via Unity is just 2 steps.
1) Create an instance of the Unity container, like this.
//Import UnityContainer container = new UnityContainer();
UnityContainer container = new UnityContainer();


2) Register your type with the Unity container. This can be done through a configuration file or thorugh code, for our example we are using the latter approach.
container.RegisterType <IService, ServiceImpl>();

3) Get the required instance from the container, using the Resolve()
DisplayClass display = container.Resolve<DisplayClass>();

The complete code example is as follows :

using System;

using Microsoft.Practices.Unity;
using Microsoft.Practices.ObjectBuilder2;
namespace unity1

{
class Program
{
static void Main(string[] args)
{
//Create the container
UnityContainer container = new UnityContainer();

//Register the our type
container.RegisterType <IService, ServiceImpl>();

//Get an instance of our type NOTE : an instance of ServiceImpl
//will in be constructor injected into the DisplayClass when it is created

DisplayClass display = container.Resolve<DisplayClass>();

display.Show();
}
}

public interface IService
{
void Show();
}

public class ServiceImpl : IService
{
public void Show()
{
Console.WriteLine("In ServieImpl Show()");
}
}

public class DisplayClass
{

private IService srv;
public DisplayClass(IService srv)
{
this.srv = srv;
}

public void Show()
{
srv.Show();
}
}
}

In this example you can see that the ServiceImple class impliments the IService interface and we register this type with the container in our
main method, also you can see that the Display class's constructor takes an instance of IService.
In our main method we create an instance out of the DisplayClass using the Resolve method of the container and whats nice is that an instance of IService is created by the container and used to instansiate the DisplayClass.

Comments

  1. You might want to double check your post - it looks like it ate all the angle brackets for the generic methods which makes things a little hard to follow.

    ReplyDelete
  2. Ye, you are correct, The code was a direct copy-past from a a running program, but I am not sure why the angel brakets did not show up...
    I'll rectify the post soon...

    ReplyDelete
  3. Ok the formating is done. Thank for the info Chris...

    ReplyDelete

Post a Comment

Popular posts from this blog

Hosting WCF services on IIS or Windows Services?

There came one of those questions from the client whether to use II7 hosting or windows service hosting for WCF services. I tried recollecting a few points and thought of writing it down.
WCF applications can be hosted in 2 main ways- In a Windows service- On IIS 7 and aboveWhen WCF was first released, IIS 6 did not support hosting WCF applications that support Non-HTTP communication like Net.TCP or Net.MSMQ and developers had to rely on hosting these services on Windows Services.With the release of IIS 7, it was possible to deploy these Non-Http based applications also on IIS 7. Following are the benefits of using IIS 7 to host WCF applications
Less development effort
Hosting on Windows service, mandates the creating of a Windows service installer project on windows service and writing code to instantiate the service, whereas the service could just be hosted on IIS by creating an application on IIS, no further development is needed, just the service implementation is n…

Task based Asynchronous pattern, Async & Await and .NET 4.5

One of the key features in .Net 4.5 is to write asynchronous programs much easier. So if I was to write asynchronous programs in .Net 2.0/3.5, I would either follow the event based model or the callback based model. For an example, a synchronous method that does intensive work (say the DoWork()) can be made asynchronous by using the following patterns
1) Implementing the IAsyncResult pattern. in this implementation, 2 methods are exposed for the DoWork() synchronous method, the BeginDoWork() and the EndDoWork() method. The user will call the BeingDoWork() passing in the required parameters and a callback of the delegate type AsyncCallback(IAsyncResult). The BeginDoWork() will spawn a new thread a return control back to the user. Once work is completed in the spawned method, as a last step, it will call the inform the AsyncResult implementation, which in turns will call the EndDoWork() (which is the callback that was passed in to the BeginDoWork()).
2) Implementing the event pattern. Her…

MEF (Managed Extensibility Framework), .NET 4, Dependency Injection and Plug-in Development

Almost after .Net 4 was released I remember reading about MEF (Managed Extensibility Framework), this was a framework for developers to compose their application with required dependencies. At first this looks like the Unity Container used for dependency injection, but MEF is much more than a dependency container but there is nothing stopping you from using MEF as a dependency injector.I remember around 5 years back when I was in a project that created a framework that allows developers to plug-in there modules as WinForm screens. The developer would create a set of screens with the intended functionalities and the drop this component in the bin folder of the framework and then will move on to do some painful configurations for the framework to pick up the module. Dropping the component into the bin folder and doing a bit of configuration is all that s needed for the framework to pick up display the screens. Typically, the configurations would also contain metadata about the screen.Al…