G
Guest
When running a 24*7 website, we need to keep the our asp.net 2.0 web
applications from restarting as much as possible. Especially during any
deployments of aspx, aspx.vb files and possible .vb classes that are in the
App_Code folder or classes in any other folder from our devlopment servers to
production.
Microsoft has claimed that any type of deployments to web applications from
development to a production web application would not cause application
restarts (lost of user's session state) with ASP.NET 2.0.
What is the definitive answer to this? What white papers can explain this?
Can anyone from Microsoft point me to the right resource to get the bottom
line answer to Web Application restarts and session state loss?
Please do not refer to "Server State" or SQL Server State" unless that is
the only solution and "inProc" session state is not the answer to this
problem.
thanks
MikeG
applications from restarting as much as possible. Especially during any
deployments of aspx, aspx.vb files and possible .vb classes that are in the
App_Code folder or classes in any other folder from our devlopment servers to
production.
Microsoft has claimed that any type of deployments to web applications from
development to a production web application would not cause application
restarts (lost of user's session state) with ASP.NET 2.0.
What is the definitive answer to this? What white papers can explain this?
Can anyone from Microsoft point me to the right resource to get the bottom
line answer to Web Application restarts and session state loss?
Please do not refer to "Server State" or SQL Server State" unless that is
the only solution and "inProc" session state is not the answer to this
problem.
thanks
MikeG