Skip to content

Latest commit

 

History

History
14 lines (11 loc) · 1.19 KB

PublishingANewVersion.md

File metadata and controls

14 lines (11 loc) · 1.19 KB

Publishing a new version

The steps to publish a new version are:

  1. Download a backup of the VSIX file from the marketplace. We want to do this in case there's an undiscovered issue with the new version and we need to rollback to the previous version. The marketplace does not provide an easy way to rollback to a previous version, and the complicated build setup of the project can make it hard to reproduce an old VSIX file, even when we are able to rollback to its commit.
  2. Update the appropriate project's source.extension.vsixmanifest file to have a new Version number; follow sematic versioning guidelines.
  3. Build the project in Release mode to generate the new .vsix file in the project's bin\Release directory.
  4. Manually uninstall the old version and install the new version using the .vsix file.
  5. Test all of the functionality to ensure nothing is broken.
  6. If the new version is working as expected, publish the new version to the Visual Studio extensions marketplace.