Fix vs2022 target#104
Merged
Merged
Conversation
Member
|
Thanks 👍 In future if you could please create a separate PR for enhancements. |
Author
|
Splitted it. New one is #105. (no conflicts) |
mistoll
force-pushed
the
FIX-vs2022-target
branch
from
bcde218 to
98c56ae
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes #103 (detect vs2022).
It also adds support for using VS Build Tools instead of VS IDE versions. Build Tools are slimmer than the IDE and are well suited for docker build images. Build tools 2019 and 2022 should both work.
Tested only with Visual Studio Build Tools 2022.