I’ve got a page with a large viewstate that appears to be tuncated during postbacks on one of our client’s server. We will minimize this in the next release.
I’m trying the maxPageStateFieldLength page attribute in web.config, but it looks like this attribute is ignored. Viewstate size is larger than the value in bytes placed in this attribute, so the viewstate should be chunked in multiple input fields, but the page is generated with a single input field.
server is 2003/IIS 6, using compression.
Naming the attribute with an uppercase M triggers an error, so i know that it is recognized (with lowercase m) but asp.net does no chunking.
It is working with the same application under VS 2005 using internal web server on my dev machine.
Any idea what might cause this attribute to be ignored?
This link explain the behavior described in my last comment. Precompilation to a non updatable web site hardcode some page parameter values in the assembly, like theme, and i just found out, viewstate chunking