State Management in ASP.NET
of the frequently asked question in Newsgroups or Usergroups is regarding
"State Management in ASP.NET". So here i will give the short decription
about various option for State management in ASP.NET and will give the links to
various article which explains detaily about various options for state
management in ASP.NET.
Is used for storing user specific data which needs to be persistant between
requests for the same page/different pages in a request.
Is Used to store Application level STATIC data (which doesn't change
This is kind of kept for backward compatibility. I prefer using Cache to store
Application level data since you have more flexibility with how you want to
manage the cache. You can even set expiration for Cache object which is not
possible using application.
can use this to store data between multiple requests to the same page.
You may use this to store data to be available per page level OR when you
want to transfer data between pages using server.transfer (but this is not the
suggested way to transfer data between pages.) the suggested way is to use page
level public properties and access them from the destination page.
have few other options like using cookies, using querystring
and stroing in database also. Since there are lots of options availble you
need to analyze use proper one which suits your application requirements
Options for Managing Persistent User State in Your ASP.NET Application
Server Controls values across pages