Fix detection of VS 2022/2026 Build Tools when VSSetup not present #242
Conversation
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
Owner
|
@psychonic Thank you so much, I will release the fix shortly. |
nightroman
added a commit
that referenced
this pull request
Nov 13, 2025
Owner
|
Done, thank you once again. |
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.
There is a regression in a7ed5d2 causing Visual Studio Build Tools 2022 to not be found when then VSSetup module is not present. This is due to the Build Tools installing to Program Files (x86) by default, rather than Program Files. The same issue also occurs with the 2026 version in the newly added support for that. The result is the ancient .NET Framework msbuild getting picked up instead.
This change falls back to Program Files (x86) for both affected versions if a corresponding install cannot be found in Program Files.