The only thing that I did not like was the semantics of constructing a view. It felt so much like the spaghetti code that I tried not to use in ASP.NET. I do see benefit, because one of the down falls with traditional ASP.NET that drove me crazy was trying to implement styling, against the traditional forms controls. I can see very good things from not being tied to those controls, making it easier to implement rich controls such as items from YUI.

My first impression is it’s all about the routes. Routes is the magic behind the curtains. Routes control what controllers are run, and how the URL is processed. MVC is a lot more than just URL handling, but coming from ASP.NET forms, good URL handling was one the major things ASP.NET was missing.

MVC is nothing new, but it is new to ASP.NET. I can’t wait to delve into it further. I see many places where I previously used ASP.NET forms where MVC would have been a better fit. I like MVC, but I could see it being over-used, and used improperly, where something like ASP.NET forms should have been used. I also can’t wait for it to go to full release, then it will be a viable option.

Bookmark It