System.Web 2.0.0.0 System.Object The HTTP requests and responses are inherently stateless. To maintain state information between HTTP requests, ASP.NET server pages can store state. This state, called view state, consists of page and control settings and data that make the page and controls appear as if they are the same ones that the user saw and interacted with on their last round trip to the server. Several mechanisms exist to store view state between successive requests to the same page. The abstract class represents the base class for these state information storage mechanisms. The default view state persistence mechanism in ASP.NET is to maintain the state information as a Base64-encoded string in a hidden HTML element (an element with the type attribute set to "hidden") on the page. An ASP.NET page uses a object to perform this work, using an instance to serialize and deserialize object state information. Alternately, you can store the view state for your pages in the object on the server using the class for mobile clients with limited bandwidth and resources. In some cases, you might disable view state persistence altogether. If you do this, the result is that sometimes pages and controls that rely on state persistence do not behave correctly. For more information about page state management and view state, see ASP.NET State Management Overview. If you are writing controls, you can store state information for the controls in the dictionary, which is a object. A developer would retrieve the control state through the property. You assign keys and values to the property, and the object serializes the state information between requests. To perform custom state handling in your control, override the and methods. Any state information that is stored in this dictionary is lost when view state is disabled by a page developer. To mitigate this, in ASP.NET version 2.0 you can store critical state information in a separate object, called control state. The control state object is not affected when view state is disabled by a page developer. Storing state information in the control state object requires that the control override the and methods and that the control be registered to store state information in control state every time the control is initialized. You can register a control to use control state by overriding the method and calling the method. For more information about using the property and control state when developing controls, see Developing Custom ASP.NET Server Controls. To maintain view state on clients that cannot support the existing view state persistence mechanisms, you can extend the class to introduce your own view state persistence methods, and you can use page adapters to configure your ASP.NET application to use different view state persistence mechanisms based on the type of client to which a page is served. Classes that derive from the class must override the abstract method to store view state and control state in the persistence medium, and override the method to extract it. If you need to serialize view state and control state to a string, you can use the object that is accessed using the property. It efficiently serializes and deserializes object state information to a Base64-encoded string. You can also override the property to supply your own object state serialization mechanism.

Provides the base functionality for ASP.NET view state persistence mechanisms.

Constructor To be added.

Initializes a new instance of the class.

The that the view state persistence mechanism is created for. 2.0.0.0 Property System.Object To be added. Control state is an object comprised of critical view state data that Web server controls need to function, and is contained in a separate object from normal view state information. Control state data is not affected when view state is disabled at the level, but requires extra implementation steps to use. For more information on using the property and control state when developing controls, see Developing Custom ASP.NET Server Controls.

Gets or sets an object that represents the data that controls contained by the current object use to persist across HTTP requests to the Web server.

2.0.0.0 Method System.Void Classes that derive from the class implement the method to initialize the and properties from some persisted format.

Overridden by derived classes to deserialize and load persisted state information when a object initializes its control hierarchy.

2.0.0.0 Property System.Web.UI.Page To be added. You can use the property to access the current object.

Gets or sets the object that the view state persistence mechanism is created for.

2.0.0.0 Method System.Void Classes that derive from the class implement the method to persist the contents of the and properties to a persistence medium.

Overridden by derived classes to serialize persisted state information when a object is unloaded from memory.

2.0.0.0 Property System.Web.UI.IStateFormatter To be added. You can override the property to provide your own view state formatter.

Gets an object that is used to serialize and deserialize the state information contained in the and properties during calls to the and methods.

2.0.0.0 Property System.Object To be added. View state is a dictionary of state data that Web server controls need to function and render themselves. Control developers typically access the view state object using the property. View state is affected when view state is disabled at the level, and as a result controls might not behave correctly in these scenarios. For more information on using and control state when developing controls, see Developing Custom ASP.NET Server Controls.

Gets or sets an object that represents the data that controls contained by the current object use to persist across HTTP requests to the Web server.

2.0.0.0