by Han C
Web developers have a choice between using ASP.NET Web Forms or ASP.NET Model-View-Controller. ASP.NET Web Forms is an older but faithful option for developers to work with in creating websites. The Model-View-Controller is essentially a newer way for developers to structure their design patterns by dividing an application up into more concise areas of focus. The article talks about the popularity and adoption of the MVC framework in IT organizations and the impact on Microsoft’s ASP.NET development platform. As usual, companies must take into consideration the costs associated with startup costs but benefits for developers start with the power of flexibility. For example, flexibility to enable development “of pure Ajax solutions without typing .a. site to a specific commercial framework. What this means is that instead of having to deal with a “thick abstraction layer built on top of Web Forms (view state, server controls, page controllers, event based page life cycle)”, MVC permits developers to build more interactive and responsive applications with components they are comfortable with such as Ajax. Furthermore, it allows programmers to have more control over the code they write.
I thought this article was interesting because I never knew there were different ASP.NET frameworks contending with one another. I had heard of ASP being an outdated technology and ASP.NET being more current. The article taught me that ASP.NET MVC was a more testable framework in regards to coding certain portions of a web application. Which can lead to a cleaner design and better thought out coding because it affords programmers more control. I feel this article is relevant to what we covered in class because we are currently working on ASP.NET in our web project. I really agree with the author of the article in that despite the complexity of design applications, there is still no real substitute for writing good clean code.
Source: Esposito, Dino. “Which ASP.NET is Better?.” Informationweek, 1307 (2011): 50-51. Proquest.