IIS 7 and Above
IIS7 no longer honors waitChangeNotification and maxWaitChangeNotific...
Last post Mar 07, 2010 11:50 AM by simone_b
May 14, 2008 11:12 AM|simone_b|LINK
IIS7 immediately shuts down the application domain when it detects changes to the root web.config file, and ignores the httpRuntime > waitChangeNotification and maxWaitChangeNotification settings. It still respects them for changes to other files in the
application, like the Bin folder, but this behavior prevents hot swapping of applications, a useful scenario introduced by those settings.
Sep 16, 2008 02:29 PM|simone_b|LINK
Anyone into this issue? It's been a showstopper for us..
Sep 17, 2008 03:04 PM|anilr|LINK
The issue that you are hitting is that is this setting is honored by asp.net and not IIS - on IIS7, IIS also listens to changes to web.config files (since it stores its settings there also) and in integrated mode, it will recycle app-domain on changes to
web.config file. Possible workarounds for this may be (a) make sure that web.config is the last file you update or (b) run asp.net in classic mode
We will look at how we can improve this in a future IIS release
Mar 07, 2010 11:50 AM|simone_b|LINK