Click here to Skip to main content
15,867,851 members
Please Sign up or sign in to vote.
1.00/5 (2 votes)
Hi,
I have an application which is developed in three tier architecture using ASP.NET and C#.
I would like to avoid the application log out or session time out whenever I modify or copy / replace the files inside the application folder.
I need the solution for both the cases like published application with .dll files and the whole application with .aspx & .aspx.cs files. Thanks in Advance.
Posted
Updated 22-Feb-15 3:55am
v2

You can not control that behavior...IIS need to recompile your site if you update some critical part of it (like a dll) and for that it need to recycle your site - that means to close all the existing connections you have...
What you may do is to store the status of your sessions (connected to the login identity) upon session end, and restore it when the same person logs-in the next time...It will not remove the need of a new login, but will take the user to the very same spot it was before...
 
Share this answer
 
Use StateServer to store your sessions and user sessions will survive site reboots.

https://technet.microsoft.com/en-us/library/cc732412(v=ws.10).aspx[^]
 
Share this answer
 
Hi,

You will face this type of problem when you are using session for user session.
Just use cookies on client side and you will be out of this problem (session expiration).
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900