Change physical path for virtual directory or site in IIS using command line for IIs6 or IIs7

appcmdasp.netdeploymentiisscripting

I need to implement some versioning for deployment for the app I support where I can copy the site to say c:\inetpub\wwwroot\app_v2 and then switch the virtual directory from c:\inetpub\wwwroot\app_v1.

Is there a way to change the physical path for a virtual directory in IIS from the command line?

Edit:

i found that in IIS7 you can use appcmd to set the physical path of a virtual directory using this format on this page Change the Physical Path of Virtual Directory Content. I was looking for something more universal….

appcmd set vdir /vdir.name:string /physicalPath:string

However, there doesnt seem to be an equivelant for IIS 6.

Best Answer

Yes, look at WMI scripting.

http://learn.iis.net/page.aspx/163/managing-applications-and-application-pools-on-iis-7-with-wmi/

http://www.aspfree.com/c/a/IIS/IIS-60-Getting-Information-Using-WMI/3/

Nick

Related Solutions

C# – An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode

The 2^nd option is the one you want.

In your web.config, make sure these keys exist:

<configuration>
    <system.webServer>
        <validation validateIntegratedModeConfiguration="false"/>
    </system.webServer>
</configuration>

Config Error: This configuration section cannot be used at this path

I had the same problem. Don't remember where I found it on the web, but here is what I did:

Click "Start button"
in the search box, enter "Turn windows features on or off"
in the features window, Click: "Internet Information Services"
Click: "World Wide Web Services"
Click: "Application Development Features"
Check (enable) the features. I checked all but CGI.

btw, I'm using Windows 7. Many comments over the years have certified this works all the way up to Windows 10 and Server 2019, as well.

Best Answer

Related Solutions

C# – An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode

Config Error: This configuration section cannot be used at this path

Related Topic