Sessions lost with new assembly

[RossT]

I have a 24x7 asp.net site for a client in the survey
business. This runs on a single web server and we use
InProc as the session choice. Authentication is required
for all users.

I'm running into a problem when I upload a new version of
the assembly/dll. All users that are logged on lose their
sessions and when they click the Submit button they get
sent back to the Login page. Since the surveys are quite
detailed, they are less than happy campers when they find
out they have to re-enter all of their data!

I now try to upload changes late at night when this will
affect the least number of users but that is just a
workaround.

Is there a way around this? Would using SQL Server as the
session manager help? If not, what????

Thanks,

Ross Terman
rterman @xeq.com

[Rad]

yes, either of the two "out-of-process" modes would help in situation like
this.
"RossT" <an*******@discussions.microsoft.com> wrote in message
news:05****************************@phx.gbl...

I have a 24x7 asp.net site for a client in the survey
business. This runs on a single web server and we use
InProc as the session choice. Authentication is required
for all users.

I'm running into a problem when I upload a new version of
the assembly/dll. All users that are logged on lose their
sessions and when they click the Submit button they get
sent back to the Login page. Since the surveys are quite
detailed, they are less than happy campers when they find
out they have to re-enter all of their data!

I now try to upload changes late at night when this will
affect the least number of users but that is just a
workaround.

Is there a way around this? Would using SQL Server as the
session manager help? If not, what????

Thanks,

Ross Terman
rterman @xeq.com

[Saravana [MVP]]

When you deploy assembly/dll in your application bin directory, then
application will reccyle i.e your appdomain is restarted. Hence session
values are lost. To avoid this go for stateserver mode or sqlserver mode.
For more details, check out this support link
http://support.microsoft.com/default...b;en-us;324772

--
Saravana
Microsoft MVP - ASP.NET
www.extremeexperts.com

"RossT" <an*******@discussions.microsoft.com> wrote in message
news:05****************************@phx.gbl...

I have a 24x7 asp.net site for a client in the survey
business. This runs on a single web server and we use
InProc as the session choice. Authentication is required
for all users.

I'm running into a problem when I upload a new version of
the assembly/dll. All users that are logged on lose their
sessions and when they click the Submit button they get
sent back to the Login page. Since the surveys are quite
detailed, they are less than happy campers when they find
out they have to re-enter all of their data!

I now try to upload changes late at night when this will
affect the least number of users but that is just a
workaround.

Is there a way around this? Would using SQL Server as the
session manager help? If not, what????

Thanks,

Ross Terman
rterman @xeq.com