What an abuse and nonsense! Is it so hard to understand that the View State is the artifact of quite unusual situation with Web applications, due to the stateless nature of HTTP protocol?
Please see:
http://en.wikipedia.org/wiki/View_State#State_management[
^],
http://msdn.microsoft.com/en-us/library/ms972976.aspx[
^].
For "normal" application thinking of a View State is nearly the same, as re-loading the whole UI desktop application on every control click (or every 10 seconds :-)) and then restoring the whole state of the state machine. For a normal desktop application developer, it would sound totally wild, but this is what actually happens with Web applications (if we forget about client-side scripting and Ajax for a moment). Applying the same thinking to desktop application is something which… well, I don't even know what to advise, perhaps starting to learn programming from the very beginning.
At the same time, saving and restoring of the status of the application when the whole application is closed and then started again is a really good thing, but this is a very different story. In all cases, you should forget the idea of View State as a nightmare, when it comes to desktop applications. However, everything can happen to a person who wish to overwhelm the application with panels so quickly. Don't even bother to explain why… :-)
—SA
Submit an article or tip