title: publishing versioned code to Service Fabric
body: <p>I think I'm either missing something in translation or the tooling is faulty.</p>
  
  <p>If i create a new .NetCore2 webapi service fabric application. (using latest SF SDK 2.7.198 and VS2017 (15.3.1))</p>
  
  <ul>
  <li>publish to local dev cluster</li>
  <li>hit the endpoint localhost:port/api/values  I get the default "value1",value2" response. </li>
  </ul>
  
  <p><strong>So i want to test a version 2</strong></p>
  
  <ol>
  <li>I add two more values in the response, or alter the response in some way.</li>
  <li>I change the manifest versions.</li>
  <li>I build the code.</li>
  <li>I package the application</li>
  <li>I publish the application to local dev cluster (ticking the upgrade option)</li>
  <li>After the upgrade finishes, hitting the endpoint (which now is marked as version2) Still gives version1 type responses. Indicating its the version one codebase.</li>
  </ol>
  
  <p>Have i missed a step here? or is this part of the tooling broken in VS2017 15.3.1? </p>
  
  <p>Also I added step 4 and 4 after i tested this previously and got the same response. But should the publish action do a build/package before it copies/publishes the codepackage?</p>