Stopping Isolated Applications
Updated: August 22, 2005
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1
|This feature of IIS 6.0 is available only when IIS is running in IIS 5.0 isolation mode.|
You can stop and unload isolated applications from memory without stopping the Web server, which makes it easier to test and debug applications.
|You must be a member of the Administrators group on the local computer to perform the following procedure or procedures. As a security best practice, log on to your computer by using an account that is not in the Administrators group, and then use the runas command to run IIS Manager as an administrator. At a command prompt, type runas /User:Administrative_AccountName "mmc %systemroot%\system32\inetsrv\iis.msc".|
In IIS Manager, expand the local computer, right-click the Web site or the starting-point directory (the directory on which the application is set) for an application, and then click Properties.
Click the Home Directory, Virtual Directory, or Directory tab. If you are in the directory that is listed as the Starting Point directory, the Application name box is filled in.
Click Remove. If the Remove button is unavailable, you are not in the application's starting-point directory.