-
Posted to
ASP.NET Administration
by
IainH
on
05-15-2007, 6:45 AM
Cheers Steve.
That led me to find the -norestart switch on the aspnet_regiis command.
Seems the default behaviour of the ASP.NET tab is to execute the aspnet_regiis command to switch .NET versions without the -norestart switch. This causes the w3 service to do a complete restart bringing down all the sites temporarily. ...
-
Posted to
ASP.NET Administration
by
IainH
on
05-10-2007, 9:41 AM
Sadly the default web site is set up to work on the 1.1 framework so I'm stuck with that set up.
I thought maybe this was an issue with my particular web server but I've managed to replicate it on 2 other Win2003s. Seems to be very odd behaviour for a web server to go down like that without warning. Maybe I'm doing something ...
-
Posted to
ASP.NET Administration
by
IainH
on
05-10-2007, 3:37 AM
Hi Tom,
Don't think this is to do with the application pool. Heres the sequence of events. I have 2 application pools - the default and one specifically for ASP2 sites.
I create the new web site which defaults to NET 1.1 and the default application pool - the folder the site is pointed to is empty.
Switch the application pool ...
-
Posted to
ASP.NET Administration
by
IainH
on
05-09-2007, 9:55 AM
Hi All,
I have an IIS server 6 on a win 2000 machine on which is installed both .NET 1.1 & 2.0 and every time I create a web site it defaults the site to 1.1. This would be fine but I’ve noticed that when I go to switch the version of the site to 2.0 in MMC in the ASP.NET tab the entire W3 service does a restart bringing down ...