Mon May 16 2011



In this months MSDN Magazine, Brandon Satrom and I released an article around migrating and ASP.NET WebPages site to MVC. A few people have asked, why would we even tackle such a topic when "no one" ( at least at this stage ) would even be considering migrating ASP.NET WebPages to MVC.

Honestly and foremost we believe it's important to understand the entire stack and how they relate to one another. When I talk about WebMatrix I always tell people it's not different.  While the Editor, RAZOR, and the page centric programming model are new, it's still built upon the same ASP.NET we have grown up with. Ok, like what? 

  • .NET ( of course ) ASP.NET Runtime Project Structure, it's just an ASP.NET WebSite project type WebDeploy SQL Compact* SEO tools

Scott Hanselman talks about getting the LEGO pieces the right size and shape, and our article is a perfect example of just that. Brandon and I were able to take an existing site and with minimal work actually convert it to MVC. Personally, I think that is a rather huge statement.  That means the migration is more about switching your underlying design pattern. Sure we have to make some code changes to support that migration but the code changes are more of "infrastructure" changes than messing around with your business logic. Yes we physically move your business logic somewhere else but we don't change it's behavior.

Having said all that awesome sauce, we kicked off the article talking about reasons on which you may or may not want to migrate.  There isn't some underlying technical reason to migrate, it's really more about a cultural preference, TDD, wicked cool build processes, separation of duty, whatever. At the end of the day it's still all ASP.NET.

I personally learned a great deal about MVC in this process and some of the "how" behind it all, I hope you do as well.