title: using visual studio team services to build a solution containing multiple web apps and deploy these web apps to azure
body: <p>My team uses Visual Studio Team Services to manage our source code in a TFS repository.  The solution contains multiple web apps.  I am trying to configure Continuous Integration and Continuous Deployment for this solution such that each web application is deployed to the correct Azure web app after a successful build.  I've configured the BuildDefinition to build $/MyProduct/MAIN/MySolution.sln.  I've defined the following parameters to MSBuild based on some MSDN articles I found on this subject:</p>
  
  <pre><code>/p:DeployOnBuild=true
  /p:WebPublishMethod=Package
  /p:PackageAsSingleFile=true
  /p:SkipInvalidConfigurations=true
  /p:PackageLocation="$(build.stagingDirectory)" 
  </code></pre>
  
  <p>The build steps include a Visual Studio Build step, a Visual Studio Test step (currently disabled to minimize complexity), an Index Sources and Publish Symbols step (which I don't think I really need), and finally, a Copy and Publish Build Artifacts step.</p>
  
  <p>I am able to build this solution using this configuration.   I can see the build results, the build log, build details, etc.  When I look at the artifacts that are created, I see two artifacts:  "drop" and "build.sourceLabel"  If I explore the drop file using the Artifacts Explorer, I find all of my projects in this drop file, and for the web app projects, I can navigate into the webapp1\obj\QA\Package\PackageTemp\bin folder and see all the DLL's etc. for the web app.</p>
  
  <p>What I don't see is one zip file per web app, which is what the Release feature of Visual Studio Team Services is expecting.</p>
  
  <p>I would like to know how to modify my current configuration so that I can generate the correct artifacts from the Build step so that I can create the correct Release Wep App Deployment tasks to deploy each web app to the correct web app in my environment.  </p>
  
  <p>This is all being done with Visual Studio 2015 and Visual Studio Online (Team Services).</p>