IoC Containers - pros and cons

[Le Rosbif]

What IoC Containers are you using (Unity, Windsor, StructureMap, Spring, ...)

Why did you pick choose a container instead of another? What are the pro and cons of the container you're currently using?

[HairyArsedBloke]

Which: Windsor
Why: It was used in the example stuff I was using (Sharp Architecture)
Pros/Cons: No idea, not used anything else. I've got my head around this one and I've got better things to do that get side-tracked into doing a comparative analysis of the various alternatives.


Doesn't help much, does it.

[Le Rosbif]

Which: Windsor

Doesn't help much, does it.

That's an understatement
I won't ask which mocking framework you use with it then

[Jaws]

I've used both Unity and Castle Windsor. Unity at ClientCo because they insist on MS everything and Windsor for some book or other.

Unity has worked fine and performed perfectly acceptable and was easy enough to use.

I noticed with Windsor it included a "WebRequest" based life time manager class. This was something I had to code manually when using Unity.

I can't really give you much more than that because I only used it to map interfaces to their respective implementations and implement some singletons.

[doodab]

I've used spring.net, the main reason for this is that I do a lot more Java than .Net and I'm familiar with the java version.

[Hex]

I use spring.net currently - it's historically what they've used and it works ok for server side but not so good for client side.

I've heard good things about http://code.google.com/p/autofac/ but haven't tried it yet. It is .net only though I think.

[Mehmeh]

Unity is nice and light weight, and easy.

I find Spring.net more complicated but you can also do more with it like Aspect Oriented stuff. Took along time to get used to it, then I loved it...hadn't used it in 2 years and started using it again at client site.... forgot how to, whoops.

I've heard lots of good things about "structure map" but never used it.

[DimPrawn]

I've only used Windsor and for Mocking Moq.

http://www.castleproject.org/container/index.html
http://code.google.com/p/moq/


Both work and do everything you might reasonably expect. Why go anywhere else?

[Jaws]

Unity is nice and light weight, and easy.

I find Spring.net more complicated but you can also do more with it like Aspect Oriented stuff. Took along time to get used to it, then I loved it...hadn't used it in 2 years and started using it again at client site.... forgot how to, whoops.

I've heard lots of good things about "structure map" but never used it.

Unity actually has the AOP stuff in the form of some method interceptor classes. I remember reading about it a while ago. I don't remember it being in version 1.0.