Several scenarios where the ASP. NET 2.0 Session was lost

1, session expiration self-fixed lost.

2. When modifying the Web. config system, restarting the SESSION will be lost.

3, the bin directory changes when the system will restart the session will be lost
(This change refers to the creation of new files, modification of filenames, modification of file contents, deletion of files, modification of directory names, deletion of directories) only when a new directory is created, the system does not restart,

4. The entire application directory is monitored by. NET and will cause the restart SESSION to be lost if there are any changes.
(The change here refers to modifying the directory name, deleting the directory)

5. A reboot is also caused when the process user name, for example: Network Service, changes permissions. Session missing

Note that if the system restarts, application, Cache, and so on will also be lost.

