title: VSTS: How to handle FileSystem WebPublishMethod in Visual Studio build step with multiple projects
body: <p>I have a solution that contains two basic (not MVC or .Net Core) ASP.Net web applications, and a few libraries on which they depend.</p>
  
  <p>I have a build definition in VSTS that contains a Visual Studio Build step, which builds the solution with MSBuild.</p>
  
  <p>The default set of MSBuild arguments package each web application into a single file, to be deployed via a batch file: </p>
  
  <p><code>/p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:PackageLocation="$(build.artifactstagingdirectory)\\"</code></p>
  
  <p>I cannot use this method, and require the website to be published to the file system so that existing scripts can do the deployment.</p>
  
  <p>Therefore I changed these arguments to:</p>
  
  <p><code>/p:DeployOnBuild=true /p:DeployDefaultTarget=WebPublish /p:WebPublishMethod=FileSystem /p:publishUrl=$(build.artifactstagingdirectory)\website</code></p>
  
  <p>This does indeed publish the two websites to the file system, but the problem is that it puts them both on top of each other in the same folder.</p>
  
  <p>Is there a way of passing some sort of paramaterised URL to <code>publishUrl</code> such that the two websites can end up in different folders? Or must I make an MSBuild step for each project individually?</p>