title: What manifest visual studio is using to generate msdeploy package
body: <p>I want to package a folder with msdeploy.exe to a zip destination at the end of CI process. 
  I run the following command line </p>
  
  <pre><code>msdeploy.exe -verb:sync -source:contentpath="C:\SampleWebApp" -dest:package="c:\SampleWebApp.zip" -declareParamFile="parameters.xml" 
  </code></pre>
  
  <p>I also like the *.deploy.cmd and *.SetParameters.xml which msbuild generates when it spits out a deployment package. I renamed the one set of  *.deploy.cmd and *.SetParameters.xml file and changed the content accordingly. to be able to run in deployment environment.</p>
  
  <p>When I run *.deploy.cmd file it generates the folder "C:\SampleWebApp" rather than creating the iis app based on parameters provided in .SetParameter.xml. </p>
  
  <p>After some investigation, I've found that the .cmd deploys to -dest:auto which is good. but apparently my package manifest inside the package indicates that this package is contentPath whereas packages generated by msbuild has more complex manifest in archive.xml inside package using iisApp provider.</p>
  
  <p>Having looked at following post </p>
  
  <p><a href="http://blogs.msdn.com/b/webdev/archive/2013/01/09/real-scenario-folder-deployment-scenarios-with-msdeploy.aspx" rel="nofollow">http://blogs.msdn.com/b/webdev/archive/2013/01/09/real-scenario-folder-deployment-scenarios-with-msdeploy.aspx</a></p>
  
  <p>I believe if I use -source:manifest="Package.xml" with right Package.xml the end result should be similar to VS package output</p>
  
  <p>The I thought maybe the *.SourceManifest.xml is the manifest for the package. I used and it builds the package but when I want to deploy that to the using .deploy.cmd it complains about setAclUser</p>
  
  <blockquote>
    <p>Error: A value for the 'setAclUser' setting must be specified when the
    'setAcl' provider is used with a physical path.</p>
  </blockquote>
  
  <p>Does anybody know that is the manifest msbuild uses?</p>