StructureMap for Dependency Injection

I decided to go with StructureMap as the dependency injection framework for my next project.  I choose StructureMap for a number of reasons.

StructureMap has been around for quite some time.  Not that this makes it better than any other framework.  However, coupled with the fact that it's an active project, it's still a hot topic in the world of DI for .NET, and a lot of .NET developers use it in their applications, I feel pretty good about it's history and future.

StructureMap 2.0 does not require an XML configuration file.  In my opinion, the last thing we need as .NET developers is another XML configuration file.  That's what I dislike the most about Java.  You can't build a J2EE application without writing a mountain of XML configuration.

Probably less of a feature and more of a convenience to me, is that StructureMap has only one purpose and that's providing a dependency injection framework to .NET developers.  Spring.NET is nice and it does a ton of things.  That scattered focus left me feeling scattered after creating a sample project using Spring.NET.  I'm sure everyone has their own feeling towards this but for me, I felt less interested in Spring.NET after reading and reading about all of the various things that framework can do.  I just wanted DI and that can be done in Spring.NET rather easily and separate from everything else the framework provides.  It's just information overload while trying to learn the one specific thing I wanted to learn.

So there you have it.  I'm excited to get started on this project and dig deeper into StructureMap.  I'll certainly provide opinions and lessons learned throughout the process.