The VIEWSTATE size is killing our apps and it keeps growing. The .aspx files are bigger than 2.5Mb in some cases. The developer is on vacation and I just installed a 90 day trial of VS 2008 to test turning form-level VIEWSTATE off then turning it on again to see if the VIEWSTATE gets reduced substantially. It didn't. It went right back to the same size. When VIEWSTATE was off the page size was 650K. With it off I tested changing one combo field and it worked. The problem is that some pages are complicated with grids and custom user controls, so I am sure that disabling it can possibly affect whether some of these fields work at all. Is this true? Our server is Win Server 2008 Enterprise. Any ideas to reduce the size of VIEWSTATE and keep the app running? I need to get this fixed today. This is an extremely important app that people across the US are using, and any help is greatly appreciated.
It's possible to develop an asp.net website with viewstate completely disabled but no-one here will be able to tell you with 100% confidence that you can disable viewstate and your website will continue to work flawlessly. It all depends on how the application has been developed and what dependency it has on viewstate.
