Compartilhar via

Web Deploy appHostConfig Provider

  • Artigo

Applies To: Windows 7, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP

appHostConfig

The appHostConfig provider synchronizes all content, configuration, and certificates for a Web site.

Example

msdeploy -verb:sync -source:apphostconfig="Default Web Site" -dest:apphostconfig="Default Web Site",computername=Server2

The appHostConfig provider returns a specified path from the IIS 7 ApplicationHost.config file or synchronizes the path from a source ApplicationHost.config file on one computer to a destination ApplicationHost.config file on another computer. The provider gathers the configuration information of the specified scope, including elements, attributes, and child elements. For a given path, if a location tag exists, the provider collects the attributes and configuration information in the scope of the location tag, including the overrideMode attribute. Inherited settings are not included.

The appHostConfig provider uses the following link extensions to synchronize application pools, SSL and server certificates, content, and the Machine.config and root Web.config files.

  • AppPoolExtension

  • CertificateExtension

  • ContentExtension

  • FrameworkConfigExtension

  • HttpCertConfigExtension

You can enable or disable these link extensions by using the -enableLink and -disableLink operation settings. For more information, see Web Deploy Link Extensions.

In a dump operation, if you use the -xml operation setting, the configuration contents, including attributes, will be displayed in XML format; otherwise, only the configuration paths will be returned.

In a sync operation, if a Web site exists in the ApplicationHost.config file that you specify for the source but not in the ApplicationHost.config file that you specify for the destination, the Web site will be created in the destination ApplicationHost.config file. You can specify different values for the source and destination paths (for example, the source site can be "Default Web Site" and the destination can be "My Site"). However, the source and destination paths must be configured at the same level; that is, a Web site path must synchronize to a Web site path, and a server path to a server path.

Important

In a sync operation, if the destination ApplicationHost.config file contains an object that does not exist in the source ApplicationHost.config file, the object in the destination ApplicationHost.config file will be deleted.

Warning

In IIS 7, any module that does not put an entry in the globalModules section of ApplicationHost.config will not be detected as a dependency. This includes most IIS-related out-of-band releases. However, IIS out-of-band releases that put an entry in the globalModules list will be detected as either native or managed modules.

Example usages

1) Display the configuration for the default Web site in XML format.

msdeploy -verb:dump -source:appHostConfig="Default Web Site" -xml

2) Synchronize settings between the default Web sites on two computers.

msdeploy -verb:sync -source:appHostConfig="Default Web Site" -dest:appHostConfig="Default Web Site",computerName=Server2