ASP.NET MVC

written by russell on May 9th, 2008 @ 08:49 AM

If you are like me, you've been developing in ASP.NET since the beginning, and you truly enjoy the development experience. Like many other .NET developers, I had some experience with VB and Classic ASP before I moved to .NET. At the time, the Page Controller model was a familiar friend from the Windows development world. Someone well versed in WinForms development could transition to web work with minimal fuss. In most cases, this still holds true today in the .NET framework.

The PostBack model in ASP.NET does a very good job of shielding the developer from the inner workings of HTTP. This speeds development time for the most part, and it lessens the learning curve for new developers. However, some developers felt that the PostBack model held back too much from the developer. This made other frameworks such as Ruby on Rails more appealing, and thus spawned projects such as Castle Monorail.

The popularity of Rails and the Castle Project (as well as other MVC frameworks) finally caught the attention of Microsoft. Which brings us to ASP.NET MVC. ASP.NET MVC is welcome addition to the .NET world--it provides a true MVC architecture for web applications. Ruby on Rails developers and Monorail developers will both see some similarity in Microsoft's implementation. In fact, Microsoft has left hooks in ASP.NET MVC for Castle Monorail components.

In the end, ASP.NET MVC won't just be a Rails clone, but rather a best of both worlds framework. True MVC architecture with the power and flexibility of ASP.NET server side controls. You can get the latest version ASP.NET MVC here and you can read up on the latest release on Scott Guthrie's blog here.

posted in:

.Net

tags:

,

accepting comments

1440 comments

Comments