tags:

views:

2605

answers:

2

Hi,

When I change the ASP.Net version of a web application in IIS 6 from ASP.Net 1.1 to 2.0. ALL sites in IIS are becoming "unavailable" (Service Unavailable) for a brief moment (the time it takes to apply the changes in the IIS dialog).

I checked with Application Pools, but the sites are all in different application pools...

How can this be?

When I change the ASP.Net version of one application, this should not affect other applications does it?

Thanks in advance,

Remco

+1  A: 

Apparently you can change the framework version outside of IIS to avoid this issue by using "Aspnet_regiis.exe". There is more information available here:

http://forums.asp.net/t/1174765.aspx

Edit: Thanks to Christopher in the comments for letting me know that using this tool is the same as an IISReset and doesn't solve the issue. :(

Jon Tackabury
Actually no - aspnet_regiis.exe causes AppDomain recycles on all application pools - the equivolent of an IISReset.
Christopher_G_Lewis
Thanks for the heads-up. I modified my answer to reflect this info.
Jon Tackabury
+3  A: 

The .Net tab in the IIS Manager is actually pretty dangerous - it will throw an IISReset at any change, and also sometimes just for spite :-)

Scott Forsyth has a blog article titled ASP.NET tab in IIS, more dangerous than it first appears! that goes over the details.

Christopher_G_Lewis