Whether we like it or not, but the requirements change over time and the Web for Developers and Architects changes with the requirements and this time the AJAX technology has been developed to make changes to the Web, Rich Internet Applications and Rich User Experience is being used as the main technology to develop.
The needs of web development have changed at the present time. For this reason, the three main Pillars on which ASP.NET WebForms Model was developed, are no longer useful for web development at the present time. Although no one knows when WebForms will reach the end of their lifetime, we all know that time is not far away.
With the development of AJAX technology, an Architecture of Request Processing also developed due to which those features were acquired through AJAX under the Pure Stateless Protocol based Web Model, which ASP.NET WebForms Model to achieve Three Pillars such as View State, Postbacks and Server Controls were defined.
So actually if we leave out these three Pillars of ASP.NET WebForms Model, then the other Classes defined for ASP.NET Model are reused as they are for any other Programming Model and the same has happened in ASP. With .NET MVC, which is based solely on the Classes and Runtime Environment developed for ASP.NET WebForms, but as a Programming Pattern named MVC.
In other words, due to the development of AJAX technology, the ASP.NET WebForms Model was unable to meet the new type of Web Requirements, so to better understand the future development of ASP.NET and the WebForms Model It is also necessary to understand the role played for the development Paradigm Shift of AJAX technology in order to use it more optimally to meet the current needs and in the following articles we will learn in detail the various aspects related to this topic.
Limitations of Using ASP.NET WebForms
View State has always been a controversial feature of ASP.NET WebForms. However, with the launch of ASP.NET 2.0, Microsoft made significant internal changes to the Implementation of the View State, so that the size of the View State was kept to a minimum and Microsoft reduced the size of the View State to about 40% in this version. Was also successful in doing.
View State is functional only for those Application Models, which are based on the maximum number of Server Controls to generate maximum Automated HTML Generate to render in Output. But when you need to create an application using the classic ASP.NET model, which requires a lot of Client-Side Interaction, Separation of Concerns (SoC), and Markup Control, then ASP.NET WebForms’ View State Feature i.e. ASP. Using one of the important Pillars named View State out of the three main Pillars of NET WebForms is not good.
Therefore, to maintain the performance, responsiveness, and interactivity of the webpage for such types of web applications, it is better to completely ignite it. Because in the present time, many Client-Side Codes are used to make more webpages based on RIA pattern, and in such web applications more postbacks are replaced with AJAX Calls to maintain page performance.
In this case, we can use WebForms to a large extent as needed, as we can use AJAX Calls to minimize postbacks, which is the most important factor affecting the performance of the Webpage. But there are some Architectural Limitations of this type of Approach, which need to be kept in mind during development.