Repository navigation
Add support for Visual Studio 2026 - #56
Merged
Merged
Conversation
alt-graph
requested review from
Finii,
Seim2k17,
ohensler,
soerengrunewald and
zykure
August 31, 2026 13:01
Finii
approved these changes
Aug 31, 2026
alt-graph
force-pushed
the
feature/support_vs2026
branch
from
August 31, 2026 13:21
f380c5b to
bac9d1c
Compare
alt-graph
marked this pull request as ready for review
August 31, 2026 13:23
[why] The heuristics for finding the VS toolchain did not know about VS 2026 yet. [how] Add "18" to the list of possible subfolder names under C:\Program Files\Microsoft Visual Studio. Yes, apparently VS 2026 uses "18" where its predecessors used "2022", "2019", or "2017".
alt-graph
force-pushed
the
feature/support_vs2026
branch
from
August 31, 2026 13:25
bac9d1c to
73ef8ef
Compare
Member
Author
|
Thanks, @Finii! |
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.
[why]
The heuristics for finding the VS toolchain did not know about VS 2026 yet.
[how]
Add "18" to the list of possible subfolder names under C:\Program Files\Microsoft Visual Studio. Yes: Apparently VS 2026 uses "18" where its predecessors used "2022", "2019", or "2017"