Comments on: IoC libraries compared

By: Benjy

Benjy — Tue, 27 Jan 2009 17:36:48 +0000

Excellent article. Maybe worth reading Ayende’s excellent post on MEF explaining why MEF is not an IoC container.

http://ayende.com/Blog/archive/2008/09/25/the-managed-extensibility-framework.aspx

By: Confluence: Java

Confluence: Java — Tue, 27 Jan 2009 13:29:36 +0000

Spring Dependency Injection…

Resources Google talks: Clean code talks on dependency injection…

By: IoC - StructureMap Links « QuantuMatrix’s Weblog

IoC - StructureMap Links « QuantuMatrix’s Weblog — Mon, 19 Jan 2009 17:24:12 +0000

[...] IoC libraries compared [...]

By: Chris Brandsma

Chris Brandsma — Fri, 16 Jan 2009 17:54:04 +0000

@Wade: I didn’t say you had to have attributes with StructureMap, I said attributes were an option. Just like Xml config…it is an option.

By: Wade

Wade — Fri, 16 Jan 2009 17:42:53 +0000

Just a note, I have StructureMap working completely free of config files and without attributes! It wasn’t mentioned in your coverage but you can register all of the objects by simply calling IAssemblyScanner.LookForRegistries() within the object factory initialization. Then in your registry file you setup fluently your contracts and defaults. No attributes needed!

By: Bryan

Bryan — Wed, 14 Jan 2009 03:03:39 +0000

I love Autofac. It’s syntax is great, it’s so simple to configure, and it doesn’t include everything and the kitchen sink (which I don’t need).

Spring’s XML configuration? I hope I never have to touch that ever again…

By: wolf++ » TuneWiz Loosely Coupled, Easily Testable

wolf++ » TuneWiz Loosely Coupled, Easily Testable — Tue, 13 Jan 2009 08:30:11 +0000

[...] feels awkward to me. I know there are tools to help with this, but I’m not ready to pick an IoC library. I don’t feel like things are complex enough to warrant it. I was just read this article, [...]

By: Weekly Links #35 | GrantPalin.com

Weekly Links #35 | GrantPalin.com — Sun, 11 Jan 2009 18:37:23 +0000

[...] IoC libraries compared Nice faceoff between different Inversion of Control libraries. Very helpful. [...]

By: Richard Dingwall

Richard Dingwall — Fri, 09 Jan 2009 20:51:02 +0000

Nice comparison. Does it worry anyone that there are so many options available? Do compelling reasons exist why each of these six libraries is best for different situations, or are some just me-too coding experiments along for the ride?

Personally, I’ve settled on Unity CommonServiceLocator. I genuinely prefer the API over most of the open-source offerings (which is rare and impressive for MS), and being part of the enterprise library, it stands out in terms of long-term supportability.

I also prefer in-code initialization. I never really saw the point of external XML/boo/whatever configuration, unless your application properly supports plugins.

By: Steve Py

Steve Py — Fri, 09 Jan 2009 04:20:20 +0000

Yeah, Nick co-wrote Autofac before getting head-hunted to M$ along with the creator of Windsor to work on MEF. I’ve worked with him on occassion including his last assignment prior to getting head-hunted. (Bastage left a big mess over here! j/k )

Autofac has my vote now due to its simplicity. We use it here with our web projects. One other thing worth noting is it has a contrib project to compliment it, and I believe a few Brisbane-ites are working on a Winform variation.

StructureMap is one I’ll be taking a closer look at this year. One tidbit I did learn over on codeBetter is that they have a diagnostic mode to inspect their XML configuration to throw a meaningful exception early rather than NullReferenceExceptions. (A bad smell I get when using IoC containers.)