Scott Hanselman

Doesn't look like they turn off view state ... instead they send a view state key instead of the state itself, storing the view state on the server for later retrieval. Interesting to do if bandwidth outranks other concerns for you. What am I missing?

I'm kind of in the same boat at phh here... It sounds like view state is left on, but simply stored server-side.

I think it actually sounds kind of cool, but that's only because I wish I could (safely) have view state for password fields :)

Either way, whatever's going on here, thanks for the link. It's interesting at the very least...

Unfortunately, ViewState is abused. We were testing components when we discovered that some of them generated an absolutely atrocious amount of ViewState (and HTML too, but that's another issue). I mean, it's pretty bad when things are slow on localhost.

We do the same technique of stashing the ViewState off somewhere, and using a key to retrieve it. Quite frankly, I don't understand why Microsoft didn't do this. If you use session storage backed by a database, it even scales across server farms.