Unity 2.0 Clarification please

Question

Could someone please help me to understand what Unity is and how it's simplifying the coding on example below:

Normal Code

FileLogger myLogger = new FileLogger();
FileLogger myLogger = new FastLogger();

Unity Container Code

// Create container and register types
IUnityContainer myContainer = new UnityContainer();
myContainer.RegisterType<ILogger, FileLogger>();       // default instance
myContainer.RegisterType<ILogger, FastFileLogger>("FastLogger");
ILogger myLogger = myContainer.Resolve<ILogger>();

Also:

What is Container in Unity?
What is Resolve?
What is RegisterType.
What is meant by Type Mapping?
What is IOC

Also what happens if two classes implement the same interface and we do something like below on Unity:

container.RegisterType<IInvoicingService, InvoicingService>()
         .RegisterType<IInvoicingService, ManagerService>();
IInvoicingService service = container.Resolve<IInvoicingService>();
service.GetCount();

Looks like it's going to invoke the getCount method on ManagerService. What should I do to invoke GetCount on InvoicingService and ManagerService?

Yes I have read the documentatation on CodePlex, it just confused me a lot!

The following anwser might help you out: http://stackoverflow.com/questions/4612054/wpf-prism-what-is-a-unity-container — Christophe Geers, Aug 26 '11 at 11:46

score 4 · Accepted Answer · 2011-08-26T12:21:54.053

For IOC and / or Dependency Injection i can recommend this read:

http://martinfowler.com/articles/injection.html

This should help you get a better understanding of what you can achieve by using this patterns. Unity helps you implement this patterns in .NET.

I will try to answer your bulleted questions with best of my knowledge:

Your Container is just that: A container. It is there for you to store your Mappings in.
"Resolve" resolves your Interface to a concrete instance of an implementation of that particular interface. However, you only will operate on that interface, therefore making the implementation exchangeable (what is the main reason for doing this whole thing)
"RegisterType" typically allows you to register a concrete class for an interface. So you basically say: "This is the interface, and if someone requests this interface to be resolved, return an instance of this concrete class". As you can see you can have default and named Type Mappings.
The Type Mapping is the mapping between the Interface and the implementation.

Thanks @UrbanEsc, appreciate it. I've added one more question on my original question. — Nil Pun, Aug 26 '11 at 12:49
@flybyte to answer your added question: you are overwriting your default registered type by not passing an argument for your second RegisterType call. To register both types you need to pass in an identifier, a literal. Then you can rssolve either the default, or the named type. Was that a clear explanation? :) — , Aug 26 '11 at 14:05

score 0 · Answer 2 · answered Aug 26 '11 at 14:43

Here's a link to a blog entry that describes unity and an example how to use it in regards to Aspect Oriented Programming (AOP) and Policy Injection. The blog also inlcudes 3 great links to MSDN artiles from Dino Espisito.

http://bardevblog.wordpress.com/2011/03/21/aop-policy-injection-with-unity/

Hope this

Unity 2.0 Clarification please

2 Answers2