title: Using MsBuild to generate customized MsDeploy manifest (Package target)
body: <p>I am using Web Deploy to package and deploy web sites for my product.  In particular, I have two different projects in my solution I use this method to deploy.</p>
  
  <p>I have a third project in the solution (a windows service) that also needs to be installed on the web server.</p>
  
  <p>I know I can write a custom manifest (for the <code>dirPath</code>, <code>filePath</code> and <code>runCommand</code> providers) and directly call MsDeploy to deploy it.  But I would like to leverage the existing MsBuild tasks to package my service if possible.</p>
  
  <p>I see it is possible to do some customization of the manifest file via msbuild targets:</p>
  
  <p><a href="http://social.msdn.microsoft.com/Forums/en/msbuild/thread/1044058c-f762-456b-8a68-b0863027ce47" rel="noreferrer">http://social.msdn.microsoft.com/Forums/en/msbuild/thread/1044058c-f762-456b-8a68-b0863027ce47</a></p>
  
  <p>Particularly by using the <code>MsDeploySourceManifest</code> item.</p>
  
  <p>After poking through the appropriate .targets files, it looks like either <code>contentPath</code> or <code>iisApp</code> will get appended to my manifest if I use the <code>Package</code> target.  Ideally I'd just like to copy an assembly (or directory), possibly set ACLs, and execute installutil.exe on the service.</p>
  
  <p>Is it possible to completely customize the manifest generated by the <code>Package</code> target, by editing my csproj file?</p>
  
  <p>If not, is there a simple way to build a new target that will do the equivalent to <code>Package</code>, yet allow me to spit out a completely custom manifest?</p>