I have an ASP.Net application being used in various time zones and countries. At anytime, there will be some users active on the application.

The application uses session to track login status of users. Whenever, I update the dll (as part of some changes / fixes), all logged in users at that time is getting logged out. Session ends. The updation needs to be done at a rate of once or twice in every week.

I am storing session In-Proc.

Is there any way I can update dll without causing session to end ?

Thanks

Madhu

Nope. This is how .NET works. The ASP.NET process puts a file/directory watch on the BIN folder for the exact reason that it will reset and reload when you overwrite those binaries.

What is it that requires you to update a live site twice a week?

-Peter

Dear Planoie,

Thank you for your reply.

Need for frequent updation is actually a mgmt. issue. This is needed because of the changing requirements posted by client. The client being very sensitive and not ready to hear future proof ideas, we are helpless. Anyway, that is not to be discussed here.

I have two doubts.

1) When we upload one of the dlls (There are many - one for each project that constitute the solution), why is the logout happens ? The dll which handles login, session storage and authentication are not changed in the near future. Is there anyway we can prevent this ?

2) If I store session in SQL server rather than in proc, can I override this problem ?

Thanks once again.

Madhu

I think, I got an answer to this problem.

I got a nice article : http://forums.asp.net/7504/ShowPost.aspx

According to this article, if I store the session in SQL server which will prevent session loss on updating dll.

I am yet to test this. I will post my experiences after testing.

ASP.NET doesn't care what actual logic is in the files you update. It just sees an update on the binaries in the virtual directory so it resets the application.

-Peter