When you push a new version out to production, it will cause an application
restart, thus ending all the sessions.
Try deploying at night, or when traffic activity is low.
bill
"PCK" <PC*@discussions.microsoft.com> wrote in message
news:7E**********************************@microsof t.com...
Thanks for the reply Matt.
No I do not rebuild on production. But I will be building in development
and then publishing to production. I assume that this would make the same
dll changes as rebuilding production. Am I incorrect to assume this?
PCK
"Matt Berther" wrote:
Hello PCK,
Presumably because the dll changes. ASP.NET has a watch on the
web.config and the dll files. If these files change, the application is restarted
(which means all previous sessions will be dropped).
I'm concerned about why this is an issue... You're not rebuilding code
on a production site, are you?
--
Matt Berther
http://www.mattberther.com
Thanks in advance for any help....
I have an application that uses the Session_End to perform some data
access against our database. This works as expected when a session
times out.
However, when the .NET project is rebuilt the Session_End is
automatically called for any current sessions. However on rebuild I
do not want my code in Session_End to be called.
Can anyone explain why the Session_End is called or have a potential
work around so that my code in Session_End is not run when the project
is rebuilt.
