Behind the scenes of ASP.NET MVC 2 – Understand the internals to build better apps

With Visual Studio 2010, Microsoft is shipping the next version of the popular ASP.NET MVC Framework with its IDE. A year ago I blogged about my findings when getting my hands on the first version of ASP.NET MVC. The MVC Framework provides really nice features that make it very easy to build web applications on top of ASP.NET. The updated support in Visual Studio also makes it very appealing to choose MVC instead of traditional ASP.NET.

The most important thing about using any framework is to understand its internals. Without that knowledge you easily run into the problem of using the framework in an unintended way resulting in problems down the road that might be hard or impossible to fix. Therefore I am going to start a series of blog posts, analyzing the internals of ASP.NET MVC 2 with the intention to educate us all about what is going on behind the scenes in order to build better applications – sounds like a plan? :-)

There are two key takeaways in this post that hopefully make you decide to read to the very end:
a) Enable Client Side Validation to reduce network roundtrips
b) Make sure you deploy your app without any debug switches on
Create a new ASP.NET MVC 2 Application

First of all you need Visual Studio 2010. It seems Microsoft offers it in a Trial version on their Visual Studio MSDN Page. Once you have it installed go ahead and create a new ASP.NET MVC 2 Application

Read more: dynaTrace blog

Posted via email from jasper22's posterous