What are the shortcomings and annoyances in Ninject and/or StructureMap DI/IoC implementations

Question

I'm looking to replace a home-grown IoC implementation with a standard one. My needs are very simple, translating an interface type into a newly created concrete class. I think you'll agree basically any framework will handle this. Currently I'm narrowing the field down to the following:

1. Ninject
2. StructureMap

So again, the question isn't what these frameworks CAN do, but more precisely where do they fall apart? What, if anything, should I be aware of before using one of these? In what ways do they annoy you? I've read a few comparisons like this one but the information is nearly a year old and not written by someone using one of these for more than a year.

Answer 1

Both of these will do the job. However, if I have to chose one, StructureMap will be the winner. Base on that it's more popular, more mature, and has greater support.

However, I believe that Ninject has a less learning curve.

Answer 2

No applicable answer