Jon Takes Five with Javier Lozano on MVC Turbine (Channel 9)

Jon Takes Five with Javier Lozano on MVC Turbine

Posted: Apr 06, 2010 at 8:26 AM

By: Jon Galloway

41,523 Views

3 Comments

Video format

Option selected may change based on video formats available and browser capability.

Auto

Use our suggested format for this video.

Smooth Streaming

Adaptive bitrate streaming - little buffering but lower video quality at times of low bandwidth. Silverlight 5 required

Progressive

Traditional buffered video format. Silverlight 5 required

HTML5

For browsers that support H.264 MP4 or WebM video playback such as:
IE9+, Firefox 4+, Chrome 5+, or Safari 4+.

Flash

For browsers that have the Adobe Flash Player plugin installed.

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

Follow
Oops, something didn't work.

Try again?

Sign In to be begin to follow these comments

What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.

Getting "follow" information

Stop following these comments

Start following these comments

What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.

Removing your "follow"

Setting up your "follow"

Did you know you can
sign up for email notifications?
- Subscribe to this comments

zowens

Apr 06, 2010 at 12:58 PM

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.
jglozano

Apr 06, 2010 at 2:02 PM

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

Sep 02, 2010 at 4:28 AM

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

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!