title: .NET Project build optimization on deployment to Azure
body: <p>I "inherited" an already existing project that consists of a few Visual Studio projects inside a Visual Studio Solution, I have deployed to Azure before, but I didn't run into my current situation.</p>
  
  <p>The project has a .NET WEB API 2 project that is already deployed on Azure, but I was asked to "separate" some components that are currently on that project into a separate API project (it's going to be deployed to another server in Azure).</p>
  
  <p>The tree structure of the code repository is like this:</p>
  
  <pre><code>tree
  .
  ├── invoice.read.api # --&gt; web api
  ├── invoice.read.bll # --&gt; business logic
  ├── invoice.read.core # --&gt; core functions
  ├── invoice.read.dal # --&gt; data access
  └── invoice.read.sln # --&gt; this is the VS solution file
  </code></pre>
  
  <p>So I have to take some of the functionality provided by invoice.read.core, and make a separate api, that's going to be deployed to another server in Azure, what I'd like to know is:</p>
  
  <p>If I were to add a new API project to the Visual Studio Solution and mark it as the startup project for the deployment, will the deployment include everything on the Visual Studio Solution (even the unused projects)?</p>
  
  <p>Or will Visual Studio deploy only what's used?</p>
  
  <p>Basically, should I make a new solution, and migrate the code that's going to be in the separate API, or is that not necessary?</p>
  
  <p>If there's any documentation on this subject you could point me to I'd be happy to read it.</p>