The document summarizes future features for ASP.NET that will improve the experience of UI/HTML developers. It discusses the history and issues with traditional WebForms and how newer approaches like ASP.NET MVC and view engines like Razor address these issues. It provides more control over markup, easier testing, and integration of UI developers alongside technical developers. However, legacy WebForms applications will still present challenges for a while.
Primary display technology – though ASP.NET is more than just WebForms Strongly Typed and compiled .aspx files taught to contain little or no code (AKA spaghetti code) - .aspx domain of UID / CodeBehind for TD Event driven – button click event / dropdown list index changed – where as the underlying web framework (Http GET Post) is more simple than that Just functions as request / response Political choice to bring across all VB windows developers to the new web paradigm Postbacks – would perform a Http Post of the entire page / form with viewstate containing the hashed value of the previous state of every servber control
How many more can they think of?
Visual Studio to show Page with Simple server controls with different client ids modes
Full test coverage is the safest way to ensure quality Many WebForm .Net developers won’t know the basic differences between a GET and a POST
Simple MVC app walkthrough Concept of Model Controller responsibility View HtmlHelpers