|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.|
How to: Read Values from View State
View state is a repository in an ASP.NET page that can store values that need to be retained during postback. For example, you can store information in view state that will be accessed during the page load event the next time the page is sent to the server. For usage recommendations, see.
View state data is stored in one or more hidden fields as base64-encoded strings. You can access view state information using the page'sproperty, which exposes a dictionary object. Because the data in view state is stored as a string, only objects that can be serialized can be stored.
To use the ViewState property, the ASP.NET Web page must contain a form element with the attribute
To read a value from view state
In page code, set the value of the variable in the ViewState property.
The following code example shows how you can get anobject named
arrayListInViewStatefrom view state and then bind a control to the object as a data source.
Dim arrayList As ArrayList arrayList = CType(ViewState("arrayListInViewState"), ArrayList) Me.GridView1.DataSource = arrayList Me.GridView1.DataBind()
Values in view state are typed as. In Visual Basic, if you set Option Strict On, you must cast view state values to the appropriate type before using them, as shown in the example. In C#, you should always cast to the appropriate type when reading view state values.
No exception is thrown if you attempt to get a value out of view state that does not exist. To be sure that the value you want is in view state, check first for the existence of the object with a test such as the following:
If you attempt to use a nonexistent view state entry in some other way (for example, to examine its type), aexception is thrown.
View state information is stored using base64 encoding and is included in the page during rendering, increasing the size of the page. When the page is posted back, the contents of view state are sent as part of the page postback information. Because this can significantly increase network traffic and slow down connections, it is recommended that you do not store large quantities of information in view state.
Another important consideration is that if the amount of data in a hidden field becomes large, some proxies and firewalls will prevent access to the page that contains them. Because the maximum amount can vary with different firewall and proxy implementations, large hidden fields can be sporadically problematic. For more information see.
Some mobile devices do not allow hidden fields at all. Therefore, view state will not work for those devices. For more information, see.
Information in view state is stored in base-64 format, but it can be tampered with by malicious users. You should treat information stored in view state as user-supplied data and always validate the information before using it. For more information about mitigating view state security risks, see. For general information about securing your ASP.NET application, see and .