title: Deploy multiple configurations from command line without changing project files
body: <p>Please don't be too harsh, because I do not grasp this entirely correctly still, but msbuild/msdeploy is giving me some headaches lately.
  Hopefully someone can provide a textual aspirin of some kind? So here is what I want to do:</p>
  
  <ul>
  <li><p>I have a web application project, that has multiple configurations, thus multiple web.config-transforms.</p></li>
  <li><p>I would like to deploy this project from command line.</p></li>
  <li><p>I would rather not want to modify its project file. (I want to be able to do this for several web applications so as least as editing as possible is much appreciated)</p></li>
  <li><p>I would like to be able to build it only once and then deploy the different configurations from it.</p></li>
  </ul>
  
  <p>So far I deployed from command line using something like this:</p>
  
  <pre><code>msbuild D:\pathToFile\DeployVariation01.csproj
          /p:Configuration=Debug;
          Platform=AnyCpu;
          DeployOnBuild=true;
          DeployTarget=MSDeployPublish;
          MSDeployServiceURL="localhost";
          DeployIisAppPath="DeployApp/DeployThis01";
          MSDeployPublishMethod=InProc
  </code></pre>
  
  <p>And this performs just what I want, except it only deploys the "Debug"-Configuration.
  How can I, with minimal adjustments, make it deploy my other configurations as well?</p>
  
  <p>I was thinking maybe I could build a package that includes all my configurations and then deploy from that and decide "while deploying" which configuration to deploy?
  Unfortuanetly I am pretty much stuck here, the approaches I have read about all seem to require some modifications to project files, is there a way around that?</p>
  
  <p>UPDATE:
  I am still not really where I want to be here :).</p>
  
  <p>But I looked into this <a href="http://sedodream.com/2011/12/24/PackageOncePublishAnywhere.aspx" rel="nofollow">PackageWeb-approach</a> (also interesting video about that <a href="http://www.youtube.com/watch?v=-LvUJFI8CzM" rel="nofollow">here</a>) and it seems pretty nice; I can now build a package that includes all my transforms and then deploy from that as often as I want into multiple configurations.</p>
  
  <p>One thing that I dislike about this is that I have to store my password in plain text into the generated parameters file for the powershell script, does someone know a way around this, I really would rather have that being an encrypted password.</p>
  
  <p>Also other approaches to solve my original problem are still appreciated.</p>