Export (0) Print
Expand All
1 out of 2 rated this helpful - Rate this topic

Web Deploy manifest Provider

Updated: March 12, 2009

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

manifest

The manifest provider synchronizes data by using directives from a custom manifest file.

Example

msdeploy -verb:sync -source:manifest=c:\MyManifest.xml -dest:manifest=c:\MyManifest.xml,computerName=Server1

The manifest provider enables you to specify a custom manifest file that contains a list of other providers that will be executed in the order that they are listed in the manifest. The provider input is a path of a single file that contains the manifest (for example, c:\manifest.xml). You can use the manifest to specify paths to different kinds of providers. For example, a custom manifest might have an appHostConfig, a contentPath, a comObject, a regKey, and a gacAssembly provider. The manifest provider processes each of these in order.

CautionCaution
The manifest provider does not perform any actions other than calling the providers that are listed in the custom manifest file that you specify. If the manifest file that you specify is invalid, the Web Deploy command will fail.

Here is a sample manifest file.


<sitemanifest>
   <appHostConfig path="mySite" />
   <gacAssembly path="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
   <comObject path="Microsoft.ApplicationHost.AdminManager" />
   <contentPath path="c:\source" />
   <regKey path="HKLM\Software\ODBC" />
</sitemanifest>

In a dump operation, a dump will be performed on each data source listed in the custom manifest file. In a sync operation, the destination's computerName provider setting will determine the computer that will receive the updates specified by the source manifest file. The manifest file that you specify for the destination can be different from that of the source, but the root element and providers specified in the two manifest files must be the same.

Example usages

1) Perform a dump on each item listed in a custom manifest file that is named CustomManifest.xml.

msdeploy -verb:dump -source:manifest=c:\CustomManifest.xml

2) Synchronize the data on a specified target computer that has the data sources listed in the custom manifest file.

msdeploy -verb:sync -source:manifest=c:\CustomManifest.xml -dest:manifest=c:\CustomManifest.xml,computerName=Server1

See Also

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.