Where is ViewState information stored?

Categories >> Software >> Microsoft Related >> ASP.NET
Suggest New Category

Question Posted / karvendhan

18 Answers
37092 Views
DSRC, HCL, I also Faced
E-Mail Answers

Answers were Sorted based on User's Feedback

Where is ViewState information stored?..

Answer / vinusreekumaran nair

Viewstate information is stored in hidden form field named
__VIEWSTATE

Is This Answer Correct ?

2 Yes

1 No

Where is ViewState information stored?..

Answer / raju

view-state allows the state of the objects and view-state
stored HTML hidden fields on the page

Is This Answer Correct ?

1 Yes

0 No

Where is ViewState information stored?..

Answer / puneet kanna

view state information store in hidden field in single encoded string and view state scoup is only for the current page

Is This Answer Correct ?

1 Yes

0 No

Where is ViewState information stored?..

Answer / prakash

SYSIBM.SYSVIEWS

Is This Answer Correct ?

0 Yes

0 No

Where is ViewState information stored?..

Answer / nagashrinivas

view state info is stored in HIDDEN FIELDS

Is This Answer Correct ?

0 Yes

0 No

Where is ViewState information stored?..

Answer / mahesh (karnataka)

Actually view state information is information about the
central governments view about a particular state in india.
I personally think that karnataka has a very good view
state... actually every state has a view state document.
Most of my friends posted in this website that it is stored
in hidden.. yes.. you people are exactly correct... it is
hidden and government will take it out when ever it is
needed and the key is with prime minister...

Is This Answer Correct ?

0 Yes

0 No

Where is ViewState information stored?..

Answer / suresh.k

Storage Options

Because it implements the Provider Pattern, you have at your
disposal two ways of storing ViewState (with more to come):

* Save To Cache: save ViewState in Cache, on the server
* Save To XML: saves ViewState into an XML file on the
server

The storage option you choose, depends on your requirements
as well as the constraints of your hosting environment.

Save To Cache: it is recommended for those situations where
you have a moderate volume of visitors. Pages will be served
faster (since we are accessing memory to retrieve
information). Since Chache is recycled automatically by the
server when memory is needed, it is important to know what
your hosting provider memory limits are, and what volume of
users you expect at any given time.
The Cache solution, allows you to specify the number of idle
minutes that you want the viewstate to be kept in memory
before being recycled (cacheMinutes attribute).
In case of premature recycling, the page will not fail, but
be redirected to itself, thus instantiating a new caching cycle.

Save To XML: it is recommended for high volume sites. Pages
will be served fast, and viewstate stored and retrieved from
xml files saved in a directory of your choice (virtualPath
attribute) that will require r/w permission.
There will be one file per user, and files will be deleted
at a configurable interval (fileCacheMinutes attribute).
Since there could be multiple ViewState in any given file
(if for example a user opens a pop-up), you can also specify
the number of minutes that any given ViewState entry can be
idle before being deleted (recordCacheMinutes attribute). If
you have a lot of pop-ups in your site, recordCacheMinutes
should be set to few minutes.
In case of premature recycling, the page will not fail, but
be redirected to itself, thus instantiating a new caching
cycle.