Click here to Skip to main content
65,938 articles
CodeProject is changing. Read more.
Articles
(untagged)

State Management

0.00/5 (No votes)
27 Feb 2010 1  
ASP.NET offers a number of places to store state, both on the client and server. However, sometimes it's difficult to decide where you should put

This articles was originally at wiki.asp.net but has now been given a new home on CodeProject. Editing rights for this article has been set at Bronze or above, so please go in and edit and update this article to keep it fresh and relevant.

ASP.NET offers a number of places to store state, both on the client and server. However, sometimes it's difficult to decide where you should put things and how to make that decision.

You choices for state management include:

  • Application - Stored on the server and shared for all users. Does not expire.  Deprecated by Cache (below).
  • Cache - Stored on the server and shared for all users. Can expire.
  • Session - Stored on the server.  Unique for each user.  Can expire.
  • ViewState - Stored in a hidden page input (by default).  Does not expire.
  • Cookies - Stored at the client. Can expire.
  • QueryString - Passed in the URL.  Must be maintained with each request.
  • Context.Items - Only lasts for one request's lifetime.  More.
  • Profile - Stores the data in the database. Can be used to retain user data over multiple request and session.

 

Whitepapers/Blogs

Videos

Enjoy! Be sure to explore the sub-topics.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here