2010: ASP.NET MVC IoC/DI - Structuremap vs Ninject, etc

Th开发者_如何学Pythonis question have been answered in 2008. End of 2010 now. Any changes? which of these IOC/DI frameworks are recommended for a very large project that will be maintained forever?

Features of this project includes:

1. WCF Web Services.
2. OData exposer.
3. Special Views for various mobile devices.
4. Repository pattern with POCO.
5. Entity Framework.

Project Structure:

1. Project Domain (Database, Repository)
2. Project Services (Logic)
3. Project Web (Views, Controllers, Service Endpoints, etc)

My personal preference is still Ninject. Excellent documentation, easy to use, drop dead simple, and gets the job done. It's our IoC of choice in all of our projects at work, and works a treat.

Side note RE something that will last forever. Wrap your IoC up in a facade so that you can swap it out down the road (we do this with our IoC, ORM, etc. just in case we have to change a few years from now).

Personally I use Spring.NET. This framework has much other features than a simple object container that can be used for DI.