When we had problems with viewstate, I started using Viewstate support software from Binary Fortress http://www.binaryfortress.com/aspnet-viewstate-helper/
This gives you a real idea of ββwhat is happening - as well as helping with the performance issues associated with the presentation in the view, you can decode the viewport with one click and see what is actually there, so you can understand which controls use viewstate and which are not, and exactly what they store there.
Also, something that no one has mentioned yet is ControlState. This happened together with ASP.NET 2, and the theory is that the important component necessary for the management function to function is in the control state, as well as data, etc. In the view, therefore, you can turn off the viewstate and bind the data to your control over each postback and control still basically work using controlstate. I say βtheoryβ because in practice, the implementation seems heterogeneous. If you look at the dropdownlist code using a reflector, for example, this is incorrectly implemented. Perhaps this has changed with later versions of the framework, I'm not sure. There is a lot of information about controlstate there, if you are looking for it, I just thought that I mentioned it.
source share