title: How vs2017-MVC project package create automatically with octopack
body: <p>Actually, the octopus server installed on my local machine, I don't want to use Build Automation tools like <strong>TeamCity, TFS, or 3rd party tools like Nant</strong>. we use MSBuild.</p>
  
  <p>New in octopus deploy, looking for idea how to get the package version unique number on each vs2017 build. So far know octopus require every package version unique, want to use MS-build command on my vs2017 project that helps me to create a unique number on each successful build.</p>
  
  <p>Recently use following the <strong>MSBuild</strong> on "<strong>Developer Command Prompt for VS2017</strong>"</p>
  
  <pre><code>msbuild 
  /t:build
  /p:RunOctoPack=true
  /p:OctoPackPackageVersion=1.0.0-BETA-1 /p:OctoPackReleaseNotesFile=ReleaseNotes.txt 
  /p:OctoPackPublishPackageToHttp=http://localhost/nuget/packages /p:OctoPackPublishApiKey=API-9MQWIWVDKR44YSGYROUGPPFBXX
  </code></pre>
  
  <p>Is there any way to use any variable with <strong>/p:OctoPackPackageVersion</strong> which increment in every build.</p>
  
  <p>I am looking for help on following</p>
  
  <ol>
  <li>After each successful vs2017 build want to create a package?</li>
  <li>How to keep new package not override previous packages?</li>
  <li>How to get a unique version number for each successful build?</li>
  </ol>
  
  <p>If have any query please ask.</p>