Fix build tools walkthrough for VS 2026.#14589
Open
sean-mcmanus wants to merge 1 commit into
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Windows 11 compiler-install walkthrough to use the current Visual Studio Build Tools WinGet package identifier, aligning the documentation with VS 2026-era tooling.
Changes:
- Switches the WinGet install target from
Microsoft.VisualStudio.2022.BuildToolstoMicrosoft.VisualStudio.BuildToolsin the Windows 11 instructions.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
Fixed by Copilot with Claude Opus 4.8 in VS Code.
It looks like Windows 10 isn't supported.
See also https://github.com/microsoft/winget-pkgs/tree/master/manifests/m/Microsoft/VisualStudio