Home/ Questions/Q 156185
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T10:17:14+00:00

I am trying to get a grasp on how to handle updates to a

  • 0

I am trying to get a grasp on how to handle updates to a live, functioning ASP.NET (2.0 or greater) Application while there are users on the site.

For example, suppose SO is an ASP.NET Web Application project. The project code compiles down to the single .DLL in the BIN folder. Now, there are constantly users on SO, so what would happen to users’ actions/sessions if you would use the Visual Studio .NET ‘Publish’ feature (or just FTP everything again manually) while they are using the site?

Would creating an ASP.NET Web Site, instead, alleviate any problems that may or may not exist with the scenario above? I am beginning to develop a web site as a user-driven Web Application, and I want to make sure that my inexperience with this would not potentially annoy the [potentially] many users that I [want to] have 24/7.

EDIT: Sorry, I should have put this in a more exact context. Assume that this site is being hosted by a web hosting service with monthly fees. I won’t be managing the server itself, just what the web host allows as a user of their services.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Changing to the asp.net web site model won’t have any effect, as the recycle will also happen, some of changes that trigger it for sure: web.config, global.asax, app_code.

    After the recycle, user will still be logged in because asp.net will just validate the syntax. That is given you use a fixed machine key, otherwise it will change on each recycle. This is something you want to do anyway as other stuff can break if the key change across requests i.e. viewstate validation, embedded resources (decryption of the url fails).

    If you can put the session out of process, like in sql server, you will avoid loosing the session. If you can’t, your code will have to consider that. There are plenty of scenarios where you can avoid using session, and others were you can wrap it and re-retrieve the info if the session was cleaned. This should leave you with a handful specific cases that you know can give trouble to the users, so for those you do some of the suggestions others have already made.

    • 0