@zowens, yes abstracting your favorite IoC container is a terrible idea since, as you stated you lose all the power and features it provides to have a lowest common denominator solution. The purpose of MVC Turbine is not to replace your IoC but to add composition to MVC applications.  I've covered this conversation before with my MVC Turbine Redux as well with podcasts, so I see no point on rehashing the information in this comment.

 

Support for IoC at all levels of an MVC application is something that's so important to ASP.NET developers that has been added to the feature roadmap for MVC3. Although MVC Turbine is not the ideal solution, it does help shed light on the issue and provides a tangible solution to this recurring theme.