Skip to content

Creating a Signed Build

Matt Bierner edited this page Apr 1, 2016 · 4 revisions

[MICROSOFT INTERNAL ONLY] These instructions kick off the build for all versions of Visual Studio installed on the machine and use the -release flag to send them for signing on our signing servers. We currently build for Visual Studio 2012, 2013, and 2015.

PreReqs

Creating a Signed Build

  1. Log into the build machine (ask Sara or Bill for machine name and permissions)
  • Our build machines have been configured and approved for use with codesigning.
  • If you're using our MicroBuild servers (which do our nightly builds), the bits will be available at: \\cpvsbuild\drops\nodejstools\NTVS_Out. Otherwise you should specify an -outdir in the next step
  1. From the PowerShell prompt that is open (or open a new one)
  2. Sync the changes (git pull origin master)
  3. Open a PowerShell prompt
  4. run .\Setup\BuildRelease.ps1 * Pass -dev -release for a dev build * Pass -name "x.y" -release for an RTM build * Pass -name "x.y zzz" -release for "Alpha", "Beta", "Beta #", "RC", "RC #" builds * Or call Get-Help .\Setup\BuildRelease.ps1 for more info

Clone this wiki locally