Thursday, May 05, 2011

Dear Microsoft ASP.NET Team: Thank you for Razor!

Since day one of using traditional ASP.NET to work with web applications, I've hated it >_> The ASP page life cycle just feels like a huge pain to me. The methodology for page processing that they invented is so wacky compared to every other web development platform I've ever used. I cried and gnashed my teeth...and just lived with it for a while.

Then, from out of nowhere, they released the MVC toolkit for ASP.NET - and I loved it. At least compared to the traditional ASP.NET page life cycle. It still seemed a bit rough when I looked at MVC2 a while back, and I never really found a project to test it out on. I ended up working more on workflow projects in Lombardi Teamworks until recently, so my research into MVC went on the back burner for while.

Now that I'm about to dive into a new ASP.NET project, I've been looking at MVC3 and the new Razor syntax - wow! Its like they actually realized that just about everything in traditional ASP.NET page development is garbage and they decided to build MVC3 and Razor to sit over top of the garbage framework and actually act like a real web development toolkit! Yay! (I know, I know, I'm being too harsh, but thats how I truly feel about it! xD )

Whatever the reasons were for making the move, I thank you Microsoft ASP.NET development team. You've made me very happy by giving me a straight forward development option. Now its time to explore the guts of how it works, and figure out how to hook into the datamodel from razor :D

For some awesome intro and tutorials for programming in Razor with ASP.NET 4:
http://www.asp.net/web-pages

1 comment:

MrC said...

From an administrative perspective, the biggest pain about ASP.NET is all the custom hooks MS built into the whole platform for what has always been, to me, no clear reason. The separate user account, the SNMP hook, and the services it installs into MS Server... The only thing more convoluted than ASP, from my perspective, is SQL. SQL Server configurations are ridiculous.

This only comes to mind because I've been designing Group Policy Objects for servers, and I keep having to re-write a policy because OH BOY THIS SERVER RUNS AAAAAASP. Bastards.