Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update vswhere to a version that supports utf-8 #1144

Merged
merged 2 commits into from
Mar 30, 2020
Merged

Conversation

bobbrow
Copy link
Member

@bobbrow bobbrow commented Mar 27, 2020

This change addresses item #1104

This fixes a text encoding issue

@bobbrow bobbrow added this to the 1.4.0 milestone Mar 27, 2020
Copy link
Contributor

@lygstate lygstate left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we need cmd.exe? can we call vswhere directly and output UTF8?

@bobbrow
Copy link
Member Author

bobbrow commented Mar 30, 2020

@lygstate I didn't write this code originally so I'm making the minimum change required to fix the scenario. If we decide to refactor the way we spawn processes in the future, we can revisit this decision.

@lygstate
Copy link
Contributor

OK, LTGM

@bobbrow bobbrow merged commit 553ea36 into develop Mar 30, 2020
@bobbrow bobbrow deleted the bobbrow/utf8 branch March 30, 2020 17:08
@bobbrow
Copy link
Member Author

bobbrow commented Mar 30, 2020

Something's wrong with the webhook. I see the build succeeded on Travis, but the status is not being reported here.

@github-actions github-actions bot locked and limited conversation to collaborators Jan 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants