@heaths heaths released this Jun 13, 2018

Assets 3
  • Add -utf8 option to force UTF8 encoding
Pre-release
Pre-release

@heaths heaths released this Jun 13, 2018

Assets 3
Create release
Pre-release

@heaths heaths released this Jun 13, 2018

Assets 3
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.

@heaths heaths released this Mar 27, 2018

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

@heaths heaths released this Mar 26, 2018

Assets 3
Update minor version for behavior change
Pre-release

@heaths heaths released this Mar 26, 2018

Assets 3
Add copy of version range for legacy-only support

Fixes #62 and #91
Pre-release

@heaths heaths released this Mar 16, 2018

Assets 3
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.

@heaths heaths released this Mar 8, 2018

Assets 3
Merge pull request #138 from Microsoft/develop

Create release
Pre-release
Pre-release

@heaths heaths released this Mar 8, 2018

Assets 3
Merge pull request #138 from Microsoft/develop

Create release