Originariamente inviato da riccardone
Per default le sessioni vengono memorizzate in uno storage presente sullo stesso web server e se riavvii l'applicazione (ad es. perchè la aggiorni) perdi le sessioni.
Le alternative a questa modalità di default che viene definita inproc sono varie.
Un articolo che può servirti per approfondire l'argomento è
http://msdn.microsoft.com/en-us/library/ms178586.aspx
p.s. anche il fw1.1 offre la possibilità di cambiare il sessionstatemode
http://msdn.microsoft.com/en-us/libr...ssionstatemode(VS.71).aspx

es.
StateServer mode, which stores session state in a separate process called the ASP.NET state service. This ensures that session state is preserved if the Web application is restarted and also makes session state available to multiple Web servers in a Web farm.

SQLServer mode stores session state in a SQL Server database. This ensures that session state is preserved if the Web application is restarted and also makes session state available to multiple Web servers in a Web farm.
non uso sql server, ma access
poi l'articolo è riferito a framework 1.1
codice:
If you are running ASP.NET 1.0 or ASP.NET 1.1, you cannot use the Aspnet_regsql.exe tool to configure ASP.NET to store session state in a persistent SQL Server database. However, you can obtain scripts to store session state in a persistent database. For details, see article 311209, "HOW TO: Configure ASP.NET for Persistent SQL Server Session State Management" in the Microsoft Knowledge Base at http://support.microsoft.com. As an alternative, Web servers running ASP.NET 1.0 or ASP.NET 1.1 can direct persistent session state to a SQL Server that has the ASP.NET 2.0 session state schema installed.