In part 2 of this series I'll create a Hello World site using ASP.NET MVC 4, and along the way you'll learn about routes, controllers, models & views.
ASP.NET MVC is seeing a lot of enthusiasm from the community right now, but not everyone is fortunate enough to be able to make the switch right away.
Some of you may be maintaining large applications where a full rewrite is not possible, or at least not in the immediate future.
That doesn’t mean there aren’t steps you can take to get your code ready for an eventual transition to MVC.
A word of warning: some of these suggestions may make you squeamish if you’re an experienced Web Forms developer who is used to using that model and accustomed to following its associated best practices.
If you like Web Forms, by all means, continue using that model to its fullest extent and take advantage of all the features it has to offer.
However if you’re looking to make the switch then keep reading and see how many of these steps you can implement in your project.
ASP.NET MVC is a programming model for ASP.NET that offers several benefits over the original programming model called “Web Forms”.
Both MVC and Web Forms are built on top of the core ASP.NET framework, meaning they each have access to the same low-level functions such as parsing requests made to the server and formatting responses.
From there MVC and Web Forms take wholly different approaches.
Hope you enjoy this, and as always I welcome your feedback. More videos planned soon!
The easiest way to reach me is to mail me at firstname.lastname@example.org.
Hi, I'm Roger and I'm a web developer with over 10 years experience.
I'll update this page soon with some new content as soon as I can think of some :-)