Home/ Questions/Q 6950759
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T14:07:55+00:00

I’m trying to understand exactly how the SessionPageStatePersister interacts with the web browser, ViewState,

  • 0

I’m trying to understand exactly how the SessionPageStatePersister interacts with the web browser, ViewState, and SessionState. I’ve been under the impression that using a PageAdapter which specifies the SessionPageStatePersister (rather than HiddenFieldPageStatePersister) will store all of ViewState into SessionState.

After inspecting the SessionPageStatePersister in Reflector I’m starting to question this assumption. It appears that the SessionPageStatePersister.ControlState property is still stored in the RequestViewStateString (SessionPageStatePersister.ViewState is stored in SessionState), when viewing the SessionPageStatePersister’s Save method.

Can anyone shed some light on this ControlState information isn’t stored in SessionState as well? It seems that the only data that needs to be stored in the RequestViewStateString is the date stamp for the SessionState key: "__SESSIONVIEWSTATE" + Convert.ToString(DateTime.Now.Ticks, 16).

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Yes, the control state stays on the page and rides up and down with the request/reponse by default. I agree that this seems pointless, but you can overcome this by add a flag to the browserCaps section in your web.config as mentioned in this article:

    http://szokelizer.blogsome.com/2006/11/09/how-to-put-controlstate-into-viewstate-and-how-to-put-viewstate-into-session/

    Check out the part toward the end for the info you need.

    I suggested to the team that they turn this setting on by default. Maybe if you vote the issue up, they will! Here’s the link for that:

    http://aspnet.uservoice.com/forums/41202-asp-net-webforms/suggestions/2454872-make-httpcapabilitiesbase-requirescontrolstateinse

    • 0