Possible Duplicate:
How to prevent an ASP.NET application restarting when the web.config is modified?
Was just thinking about uptime. Thanks.
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
Yes, you can; see this answer.
However, it is not a good idea.
Until ASP.Net restarts the AppDomain, it will not look at web.config.
If you change web.config, your changes will have no effect until the AppDomain is restarted.
Method 2
You can create an external settings file and then reference it in your web.config. You will need to change the attribute “restartOnExternalChanges” to false in your machine.config file.
See:
http://msdn.microsoft.com/en-us/library/ms228057.aspx
Method 3
You can setup a duplicate IIS container on a different ip address / hostname. Make your modification to the new version and then swap the ip’s over. It gets rid of the compile time of the application restart. However, if you rely on in-proc session it’ll all go wrong for any current users anyway.
Safest option is to allow it to restart and just pick a good time to do it. You can also set compilation batch = false. This can also speed up the compile time in critical systems.
Method 4
The application pool will reset when you modify the wed.config and you will lose any session information stored on the server.
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0