Session state is used to maintain data for an individual user
for the duration of their interaction with a web site. Our
application used an “InProc” session, which maintained state in
memory. This made development painful because a recompile forced
a new login to the web site. We changed to an “SQLServer”
session which solved the login problem; you can just carry on
where you are after a recompile. Asp.net, Session State,
web.config, Sql Server. Session State is defined in the
web.config file: <configuration> <system.web> <sessionState
mode="InProc"/> - InProc: stores session state in memory on the
Web server. (Default). - StateServer: stores session state in a
separate process called the ASP.NET state service. This
preserves state if the Web application is restarted and also
works in a server farm model. - SQLServer: State is preserved in
Sql Server. To configure SQLServer mode: - In web.config:
<sessionState mode="SQLServer" sqlConnectionString="Data
Source=(local);Integrated Security=SSPI;"/> - From a VS