title: Using msdeploy with setParamFile and declareParamFile over a filesystem directory
body: <p>In an automated deployment scenario where I need to apply entity framework migrations in various environment I would like to apply msdeploy style parametrization over a non web project with declarations and values parameters xml files.  </p>
  
  <p>It's easier for us because we already maintain declarations/values xml files for other web projects and this way we would tiny all our parametrization to the same place and be able to reuse our existing logic for applying parametrization over various project.  </p>
  
  <p>My first though was just to copy the existing migration project to a 'work' folder, where msdeploy would apply parametrization. So I went with the <code>dirpath</code> provider and I specify both the declarations and values xml files:  </p>
  
  <pre><code>msdeploy
    -verb:sync
    -source:dirPath="c:\Sources\Project.Migrations"
    -dest:dirPath="c:\work\Project.Migration"
    -setParamFile:"c:\Deployment\SomeEnv\Project.Migrations.SetParameters.xml"
    -declareParamFile:"c:\Sources\Project.Migrations\Parameters.xml"
  </code></pre>
  
  <p>Nevertheless, it fails with the following error:</p>
  
  <pre><code>EXEC : error : The 'MSDeploy.dirPath' object does not support declared parameters.
  </code></pre>
  
  <p>The <a href="http://blogs.msdn.com/b/spike/archive/2012/10/12/using-msdeploy-to-update-and-remove-sections-in-web-config-a-simple-example.aspx" rel="nofollow">following link</a> shows an exemple of using Parameters.xml with dirPath provider.<br>
  But both value and declaration are mixed up in the same file which I would like to avoid.  </p>
  
  <p>Is there a way I could have both declaration and values files split up ?</p>