December 2009 Entries
I would like to thank Rob Conery for posing the question:
As the project’s portal states:
MVC Turbine is a plugin for ASP.NET MVC that has IoC baked in and auto-wires controllers, binders, view engines, http modules, etc. that reside within your application. Thus you worry more about what your application should do, rather than how it should do it.
Let’s see how this plays out for your application…
Plain Old MVC Application
If you create an MVC application by using File –> New, you get the full power of the MVC framework but your application is not yet setup to take full advantage...
The MVC Turbine bits are now compiled against ASP.NET MVC 2 Preview 2 Beta and Visual Studio 2010 and .NET Framework 4 Beta 2. You can get the bits by going to the CodePlex site.
Please note that this the same feature release as MVC Turbine v2.0 RTM. The following is compiled and upgraded to work with .NET4 in VS2010:
Runtime binaries
Feature Samples
Nerd Dinner Sample
Okonau Sample
From here on out, the main development will take place onVS2010 and MVC2 as I get things setup for v3...
Since the release of MVC Turbine, I’ve been getting lots of questions about the design decisions I made around the interaction with the Service Locator that ships with the plug-in. The two main questions are: Why didn’t you use the Common Service Locator project from CodePlex? Why are we forced/constrained/etc to use generic component registration API? These questions are very valid and could be easily explained if I ever write the documentation for the project (which, I’m working on by the way). So in this post, I hope to...
Can you answer at least one of the following questions: Are you an ASP.NET or related web technology enthusiast? Are you going to be in Bellevue, WA on 2/16 for the MVP Summit? Do you live in the Seattle area? Do you like to eat/drink with fellow geeks? If you have answered at least one of these questions, come hang out with us at ASP.beer! When: Feb 16, 2009 @ 8:00 PM (PST). Where: Tap House Grill, 550 106TH AVENUE NE BELLEVUE, WA...
I’ve blogged in the past about the extensible component model for MVC Turbine, this post is a continuation on that concept, except with views as embedded resources. Virtual Path Provider: The Secret Sauce Not sure how many of you know this, but a VirtualPathProvider (VPP) is a way to provide the ASP.NET runtime with resources from a virtual file system. In other words, you can provide files such ash web forms, scripts or anything else that’s served to the ASP.NET run time to process. To learn how to this more in detail, check...
Well, here’s the official blog post for the tweet I did last night: I figured, I should tweet the release and have people get an early access to it, then blog the same (plus more) information here. :) What is MVC Turbine? I’ve been asked many times for the 140 char description of Turbine, so here it is for the record: MVC Turbine is a plug-in for ASP.NET MVC that has IoC baked in and auto-wires controllers, binders, view engines, http modules, etc. that reside within in your application. Thus...