none
Web.Config Vs IISReset

    Question

  • Hi All,

    Can any of you tell me, if changing web.config causes IISReset for MOSS application ?

    If yes, does it happen all the times or is that limited to specific entries in web.config ?

    regards,

    Srikanth Gutha

     

    Wednesday, January 28, 2009 7:51 PM

Answers

  •  

    This blog will answer your questions, Thoughts on IIS Configuration Changes and when it takes effect (http://blogs.msdn.com/david.wang/archive/2006/03/12/Thoughts-on-IIS-Configuration-Changes-and-when-it-takes-effect.aspx)

     

    I quoted the words from the blog for your information:

     

    All I can tell you is that the product teams for both IIS and ASP.Net try to make as many of their configuration changes take effect immediately... without requiring a reset of anything... except for the few changes that are "global" in scope or otherwise hard to synchronize without recycling worker processes or restarting IIS.

     

    Unfortunately, it is not easy for us to enumerate the settings and their behaviors because it is often tied to implementation details. For example:

     

    ISAPI Filters changes do not all process the same way - site ISAPI Filters can be added and removed and immediately take effect, but global ISAPI Filters require restarting IIS (in IIS5 Compatibility Mode) or recycling the application pool ( in IIS6 Worker Process Isolation Mode) to take effect.

    Application Pool settings take effect on startup of the application pool's worker process(s)... so you can control whether every application pool property change causes a recycle (i.e. changes take effect immediately) or that settings take effect on the subsequent recycle through whatever means.

    Anyways, here are the answers to your specific questions. None of them require IISRESET, and many take effect immediately:

     

    On IIS6, web.config is an ASP.Net concept totally unrelated to IIS. Any change in the web.config file triggers a reload of the AppDomain, so settings from the web.config take effect immediately. No iisreset/recycle required.

    Changing IIS Virtual Directory settings take effect immediately, no iisreset/recycle required.

    Updating DLL files in the ASP.Net /bin directory trigger a reload of the AppDomain so changes take effect immediately. Updating ISAPI DLL files is a little more complicated, as described in this blog entry, and require a recycle of the application pool.

    Updating ASPX files trigger a recompilation and reload of the AppDomain so changes take effect immediately. No iisreset/recycle required.

     

    Hope the information can be helpful.

    -lambert


    Posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, February 03, 2009 2:24 AM

All replies

  • Not a Programming question. 

    Moving to Admin.

    WSS FAQ sites: WSS 2.0: http://wssv2faq.mindsharp.com WSS 3.0 and MOSS 2007: http://wssv3faq.mindsharp.com
    Total list of WSS 3.0 and MOSS 2007 Books (including foreign language titles) http://wss.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/V%20Books.aspx
    Thursday, January 29, 2009 6:05 AM
  •  

    This blog will answer your questions, Thoughts on IIS Configuration Changes and when it takes effect (http://blogs.msdn.com/david.wang/archive/2006/03/12/Thoughts-on-IIS-Configuration-Changes-and-when-it-takes-effect.aspx)

     

    I quoted the words from the blog for your information:

     

    All I can tell you is that the product teams for both IIS and ASP.Net try to make as many of their configuration changes take effect immediately... without requiring a reset of anything... except for the few changes that are "global" in scope or otherwise hard to synchronize without recycling worker processes or restarting IIS.

     

    Unfortunately, it is not easy for us to enumerate the settings and their behaviors because it is often tied to implementation details. For example:

     

    ISAPI Filters changes do not all process the same way - site ISAPI Filters can be added and removed and immediately take effect, but global ISAPI Filters require restarting IIS (in IIS5 Compatibility Mode) or recycling the application pool ( in IIS6 Worker Process Isolation Mode) to take effect.

    Application Pool settings take effect on startup of the application pool's worker process(s)... so you can control whether every application pool property change causes a recycle (i.e. changes take effect immediately) or that settings take effect on the subsequent recycle through whatever means.

    Anyways, here are the answers to your specific questions. None of them require IISRESET, and many take effect immediately:

     

    On IIS6, web.config is an ASP.Net concept totally unrelated to IIS. Any change in the web.config file triggers a reload of the AppDomain, so settings from the web.config take effect immediately. No iisreset/recycle required.

    Changing IIS Virtual Directory settings take effect immediately, no iisreset/recycle required.

    Updating DLL files in the ASP.Net /bin directory trigger a reload of the AppDomain so changes take effect immediately. Updating ISAPI DLL files is a little more complicated, as described in this blog entry, and require a recycle of the application pool.

    Updating ASPX files trigger a recompilation and reload of the AppDomain so changes take effect immediately. No iisreset/recycle required.

     

    Hope the information can be helpful.

    -lambert


    Posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, February 03, 2009 2:24 AM