The size of the hidden view state field has no limit. However, some proxy servers and firewalls refuse to let pages through if they have hidden fields greater than a certain size. To circumvent this problem, you can use view state chunking, which automatically divides view state into multiple fields to ensure that no hidden field exceeds a size threshold you set.
To use view state, you simply need to set the maxPageStateFieldLength attribute of the
element in the web.config file. This specifies the maximum view state size, in bytes. Here’s an example
that caps view state at 1 KB:
When you request a page that generates a view state larger than this, several hidden input fields will be created:
Remember, view state chunking is simply a mechanism for avoiding problems with certain
proxies (which is a relatively rare occurrence). View state chunking does not improve performance (and adds a small amount of extra serialization overhead). As a matter of good design, you should strive to include as little information in view state as possible, which ensures the best performance.
To use view state, you simply need to set the maxPageStateFieldLength attribute of the
element in the web.config file. This specifies the maximum view state size, in bytes. Here’s an example
that caps view state at 1 KB:
When you request a page that generates a view state larger than this, several hidden input fields will be created:
Remember, view state chunking is simply a mechanism for avoiding problems with certain
proxies (which is a relatively rare occurrence). View state chunking does not improve performance (and adds a small amount of extra serialization overhead). As a matter of good design, you should strive to include as little information in view state as possible, which ensures the best performance.