It won’t be long before Microsoft release their new MVC framework for ASP.NET. Just looking at a huge list of MVC frameworks for other web languages shows that there is certainly something going on. Java MVC frameworks, such as Spring and Struts are mature and very popular (our own Java line-up contains many books on MVC frameworks).

It’s also quite apparent that most of the MVC frameworks (and certainly all the main ones) are in open source-friendly languages that don’t necessarily have the backing or tools that Microsoft give ASP.NET. This seems to have lead to a situation where developers needed to create easier, more efficient ways of writing web applications. Microsoft are now at least trying to redress this (and in common with a previous post this is another sign that .NET is growing up as a mature technology).

I’ve read a few message boards here and there (mostly from a few years ago) that ask about third-party MVC frameworks for ASP.NET, but those queries are scattered and the discussions peter out. However, the general consensus about the latest announcement is that the Microsoft MVC framework is going to be fairly interesting. It’ll save you from ViewState and postbacks to manage state, gives you the chance to use custom URLs, and increases the separation of your components. I think it’s a fine idea.