How To Keep ASP.NET ViewState On The Server – Revised

This is a follow up post to Basic Sample - How To Keep ASP.NET ViewState On The Server

ASP.NET 2.0 offers much easier built-in mechanism to save ViewState on the server in Session using SessionPageStatePersister. Thanks to Russ who pointed me to this feature available in ASP.NET 2.0 via comments in the previous post.

The details can be found here ASP.NET 2.0 Page State Persister [thanks go to Eddie from our own ACE team for the pointer].

Short analysis. Using SessionPageStatePersister to store VIewState is very convenient as there is no code needed, almost. The down side is that this approach allows storing ViewState only in Session while the approach described in previous post allows routing ViewState to any storage of your choice – Session, Cache, DB, Web Services – up to your imagination. This can be important when considering scalability aspects of the solution that kazlak pointed out in the comments for the previous post.

To commentators. Big-thank-you for leaving your insightful comments. Sharing your insights helps me to improve and I am sure it also enriches this blog readers experience – THANKS! Please comment more and leave your web sites/blogs so I can link back to you and give you full credit to your insights.

Comments (2)
  1. alik levin's says:

    Building ASP.NET web applications? Plan to serve thousands of users? Would you like to see how your application

  2. [Ed. – Guy, apologies for originally calling you Eran.. shy] PDD – Performance Driven Development presentation

Comments are closed.

Skip to main content