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.
Enjoy! Be sure to explore the sub-topics.
The ASP.NET Wiki was started by Scott Hanselman in February of 2008. The idea is that folks spend a lot of time trolling the blogs,
live-searching for answers to common "How To" questions. There's piles of fantastic community-created and MSFT-created content out there, but if it's not found by a search engine and the right combination of keywords, it's often lost.
The ASP.NET Wiki articles moved to CodeProject in October 2013 and will live on, loved, protected and updated by the community.