Web Forms State Management
Web Forms pages and the ASP.NET page framework use HTTP to communicate between browser or client device and the Web server. HTTP is a stateless protocol, meaning that it does not automatically indicate whether the requests in a sequence are all from the same client or even whether a single browser instance is still actively viewing a page or site. In addition, each time a page is processed in a round trip, it is destroyed and rendered anew, and all information about the state of the Web Forms page and the controls on that page are lost.
As a result, building Web applications that need to maintain cross-request state information — for example, showing a shopping cart or paging through data — can be extremely challenging without additional infrastructure help.
The following topics provide a general background and how-to information on how you can manage state in your Web Forms pages.
In This Section
- Introduction to Web Forms State Management
- Provides an overview of how values are preserved in a Web Forms page during round trips to the server.
- State Management Recommendations
- Provides an overview of the advantages and disadvantages of state management techniques available in ASP.NET.
- Saving Web Forms Page Values Using View State
- Provides information on how to store information in view state (in the page) between round trips.
- Passing Values Between Web Forms Pages
- Describes how to redirect one Web Forms page to another and pass information to the target page.
- ASP.NET Applications
- Provides information on additional topics of interest concerning Web Forms and pages ASP.NET applications.
- ASP.NET State Management
- Provides information on ASP.NET state management.
- Programming Web Forms
- Provides information on programming in Web Forms pages.
- ASP.NET Server Controls
- Provides information on server controls provided by ASP.NET.
- Web Forms Pages
- Gives an overview of Web Forms technology in ASP.NET.
- ASP.NET Server Control Event Model
- Provides information on the Web Forms control event model.