Web Deploy Providers

Artigo
07/02/2012

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

Providers process specific source or destination data for Web Deploy. For example, the contentPath provider determines how to work with directory, file, site, and application paths. On the Web Deploy command line, the provider name is specified immediately after the -source: or -dest: argument.

In most cases, the source and destination providers will be the same (for example, you cannot synchronize a metaKey provider with an appHostConfig provider). However, you can use the package and archiveDir providers in combination with other source or destination providers to restore or create packages or archives.

If you would like to use more than one provider for a source or destination, you can create a custom provider by combining two or more providers by using the manifest provider. For more information, see Web Deploy manifest Provider.

For more information about each provider, see the following links.

Web Deploy appHostConfig Provider

Web Deploy appHostSchema Provider

Web Deploy appPoolConfig Provider

Web Deploy appPoolEnable32Bit Provider

Web Deploy appPoolNetFx Provider

Web Deploy appPoolPipeline Provider

Web Deploy archiveDir Provider

Web Deploy auto Provider

Web Deploy cert Provider

Web Deploy comObject32 Provider

Web Deploy comObject64 Provider