title: How to allow for multiple types deployment?
body: <p>In my search for the <a href="https://martinfowler.com/articles/microservices.html" rel="noreferrer">meaning of life</a>, I stumbled upon a blog post that mentioned that <em>your deployment strategy is not your architecture</em>, it is simply an <em>implementation detail</em>, and as such we need to design for allowing different deployment <em>patterns</em>, whether you want to deploy your system to 1 node or multi-node, or another type of structure. </p>
  
  <p><strong>Do the latest versions of Visual Studio provide some kind of flexibility (besides azure) to be able to deploy services in a variety of strategies?</strong> </p>
  
  <p>For example, let's say I have a solution</p>
  
  <pre><code>    Acme Solution
      --Acme Startup Proj
      --Acme Service A.csproj
      --Acme Service B.csproj
      --Acme Service C.csproj
  </code></pre>
  
  <p>I want to be able to deploy this entire solution as 1 solution, or I would like to be able to deploy 3 separate binaries, one for each <strong>micro</strong>service.</p>
  
  <pre><code>AcmeServiceA.exe
  AcmeServiceb.exe
  AcmeServicec.exe
  </code></pre>
  
  <p><strong>What does Visual Studio give you in terms of flexibility of deployment configuration?</strong></p>