Home/ Questions/Q 7780079
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T18:48:27+00:00

I have a complicated, very involved ASP.NET WebForm with a large ViewState . Currently,

  • 0

I have a complicated, very involved ASP.NET WebForm with a large ViewState. Currently, to lower impact in the browser (by shrinking the __VIEWSTATE hidden input field), I use a PageAdapter and SessionPageStatePersister to store the ViewState within the Session.

However, I want to change my session mode from InProc to StateServer, so that I can both lower my RAM usage and avoid site restart and application pool recycling issues. Will I need to pull the ViewState back out of the Session? Or can it remain as is?

In the future, I’ll want to load balance, also, but I heard that I could just use “sticky sessions”, so that might not force me into StateServer.

NOTE: I’m currently using .NET 2.0 (Integrated), but I’m open to updating that.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    SessionPageStatePersister stores your Viewstate in the Session object wherever your Session happens to be stored. It’s completely agnostic about whether your session is InProc, SQL or StateServer, it should just keep working without you having to do anything.

    • 0