I've used both StructureMap and Unity in anger. These days I'm almost entirely using Unity. Some of our clients require us to declare any 3rd party libraries we use in development and the Microsoft Patterns and Practices block is usually already cleared for use.
While Unity may not strictly speaking be the best out there, my company and many of our clients have standardized on it. It's definitely quite capable, yet simple enough, and I don't find myself wishing for any other IoC container. You could probably poke a stick at any one of the popular ones and find they'll all fit your needs. On Mon, Feb 21, 2011 at 10:24 AM, Michael Minutillo < michael.minuti...@gmail.com> wrote: > I guess it's still early in the day but I'm surprised not to see any > StructureMap/Windsor peeps throwing their hats in the ring. > > Back to the original point, most of the containers will provide many of the > same capabilities but in slightly different ways. At the end of the day > there are only so many ways you can build a dictionary of object factories > (which is sort of all an IoC container is). Most of the time the differences > are in how you register components with the container and some of these > features can get quite advanced so by the time you need those, you've > already made your choice. > > If you have the time, the best thing for you to do is to build a very small > app representative of the way you'll be doing things and then try each of > the containers out to see how they "feel". > > > > On Mon, Feb 21, 2011 at 10:13 AM, Joseph Cooney > <joseph.coo...@gmail.com>wrote: > >> I <3 Autofac. >> >> On 21/02/2011, at 10:23 AM, Bec Carter <bec.usern...@gmail.com> wrote: >> >> > G'Day, >> > >> > What IoC containers do you all recommend? There are so many around! >> > >> > Cheers, >> > Bec >> > >
