Rate It (6) Thank you for your feedback!
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.
Enjoy! Be sure to explore the sub-topics.
Revision number 1, Monday, February 04, 2008 8:00:00 AM by This is not the most up to date version of this article. The most recent version can be found here.
You must Login to comment.
Cool main page for state management
Session
The Session Object is one of the easiest to use and most useful aspects of ASP.NET. There are some caveats to its use when building very large systems and Web Farms, so it pays to be educated. How To Basics of ASP.NET Session State- Start here with this excellent
ViewState
ViewStateis the mechanism that allows state values to be preserved across page postbacks. Because of the stateless nature of web pages, regular page membervariables will not maintain their values across postbacks. When we need a page variable to maintain its
Application and Cache
The Cache and Application objects provide broader scope than the Session object and the data is available to all the classes within theASP.NET application. The Basics ASP.NET Application State Overview ASP.NET Caching Overview How to: Save Values in Application
Cookies
Cookies are small amounts of text that can be stored on the client pc by the browser. The cookie can be accessed both at the client through the use of Javascript and also at the server. While cookies can be a convenient way to store small bits of state information
(last 30 days)
Advertise Here