With so many IoC containers is there a decision matrix to help in narrowing them down based on features, supported platforms, etc.?
+4
A:
More is certainly better than less.
There's a good comparison on this blog. And part 2 here.
Mircea Grelus
2009-07-16 23:06:04
The comparison led me to use autofac, w/ great results
Scott Weinstein
2009-07-16 23:32:54
Note, ninject IMHO is one of the cleanest and most complete IoC containers, it has had a LOT of updates in the last 6 months http://github.com/enkari/ninject/network
Sam Saffron
2009-07-16 23:42:48
I'd put a vote on NInject too... considering I decided to try and understand the source, and it was so clean and well factored I had no trouble following it on first reading.
jerryjvl
2009-07-16 23:46:46
This is the best comparison so far. It is somewhat limited on the number of IoC frameworks covered and missed some features that are important to my project such as Compact Framework support (NInject supports CF).
Jason Morse
2009-07-20 17:12:21
The community really needs a wiki that can be kept up to date for this.
Derek Greer
2009-10-08 03:15:10
A:
Another one worth looking at is MEF, it's not strictly an IoC container, but employs many of the same techniques. The important thing to keep in mind is that it is going to ship with .Net 4.0.
I really love the way Nate does stuff with Ninject, it is so clean and a very active project and I would strongly recommend it (even over MEF).
Make sure you look at the history of check-ins for all your candidate containers, if there are few to no updates in the last 6-12 months I would stay clear of them, no matter what the comparison matrix says.
Also, I would look at the test cases for the frameworks, and make sure they make sense. You don't want to be stuck with a over complicated IoC container.
Sam Saffron
2009-07-16 23:47:25