2.5.9

Changes:

• 725b7a3 Fix copyright in nuspec
• 8174919 Merge pull request #160 from Microsoft/develop
• 3c3e7ce Update triggers for PR,CI builds
• 236e409 Write state properties [ #133 ]
• 9808946 Migrate to Azure Pipelines
• da3e71d Remove localized dates from tests
• 1d815f2 TextFormatter function missing "override" keyword

This list of changes was auto generated.

2.5.2

• Add -utf8 option to force UTF8 encoding

2.5.2+gebb9f26a3d

Create release

2.5.1+g2444e2e409

Add -utf8 option to force UTF8 encoding

Attempt to fix #146. The console host and shell's output encoding still play a major factor, however. In cmd.exe, you still need to set chcp to display strings. In powershell.exe, you need to set chcp to display strings and use [Console]::OutputEncoding = 'UTF8' when redirecting to a file (which will itself encode as Unicode). The -utf8 switch does, however, fix the problem in testing with Node's child_process.execFile.

2.4.2+g626dfa3e71

Fix regex refspec in version.json

2.4.1

• Fixed #62, #91: -version supported even when Visual Studio 2017 or newer is not installed.

2.4.1+g2035d08a45

Update minor version for behavior change

2.3.9+gf7b87a2559

Add copy of version range for legacy-only support

Fixes #62 and #91

2.3.8+g7b5d10f7fc

Improve tests for -latest

A bug was found in the VSSetup.PowerShell project that didn't correctly implement -latest. vswhere did but I wanted to unify the tests to make sure the right behavior is not regressed.

2.3.7

Merge pull request #138 from Microsoft/develop

Create release