Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Jon Takes Five with Javier Lozano on MVC Turbine

9 minutes, 59 seconds


Right click “Save as…”

In this video, Jon talks to Javier Lozano about MVC Turbine.

MVC Turbine is an open source plugin for ASP.NET MVC that has IoC baked-in and auto-wires controllers, binders, view engines, and http modules, etc., that reside within your application. The goal is to let you focus on what your application should do, rather than how it should do it.


Follow the discussion

  • Oops, something didn't work.

    Getting subscription
    Subscribe to this conversation
  • Abstracting your favorite IoC container is a really terrible idea. Why would you use Unity over StructureMap over NInject, etc if you're just going to abstract away the power? Doesn't make a lot of sense from an architectural perspective. Why take on an additional dependency that is just an abstraction on IoC and dependency containers, wire-ups, etc?


    And another thing... infered actions. Why would you use MVC if you're just returning a view? Smells exactly like webforms at that point.

  • @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.

  • Exactly, it's not about abstracting your favorite IoC container, it's just a by-result of not taking a dependency on a specific container which is a bigger gain than lose in case of MVCTurbine, you still can use 99% of the power of your favorite container (and its extensions).


    @jglozano: I watched the video and the idea of injecting dependencies into http modules is seeeet Smiley

    The 2.1 bits are great giving you ways to cover for the 1% of less common scenarios if you really need that and know the drawbacks.

    Good luck with the project!


Remove this comment

Remove this thread


Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.