Can you modify the web.config and NOT restart the ASP.NET application?

Question

Possible Duplicate:
How to prevent an ASP.NET application restarting when the web.config is modified?

Was just thinking about uptime. Thanks.

Answer 1

The application pool will reset when you modify the wed.config and you will lose any session information stored on the server.

Answer 2

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.

Answer 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.

Answer 4

Another thread on the matter

Answer 5

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