Skip to content
This repository was archived by the owner on Apr 2, 2020. It is now read-only.

Don't use legacy pre-VS2017 logic if we successfully launched VS via vswhere#114

Merged
hach-que merged 1 commit intoProtobuild:masterfrom
hach-que:vswhere-fix
Aug 26, 2017
Merged

Don't use legacy pre-VS2017 logic if we successfully launched VS via vswhere#114
hach-que merged 1 commit intoProtobuild:masterfrom
hach-que:vswhere-fix

Conversation

@hach-que
Copy link
Copy Markdown
Member

This second block needed to be guarded so that we don't accidentally launch two instances of Visual Studio.

…vswhere

This second block needed to be guarded so that we don't accidentally launch two instances of Visual Studio.
@hach-que hach-que merged commit 7212eb7 into Protobuild:master Aug 26, 2017
@hach-que hach-que deleted the vswhere-fix branch August 26, 2017 17:42
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.

2 participants