Fix dev setup .vsconfig component IDs for Visual Studio 2026#48824
Open
niels9001 wants to merge 1 commit into
Open
Fix dev setup .vsconfig component IDs for Visual Studio 2026#48824niels9001 wants to merge 1 commit into
niels9001 wants to merge 1 commit into
Conversation
The winget configuration files now provision Visual Studio 2026 (channel 18.Release), but .vsconfig still listed Visual Studio 2022-era component IDs that were renamed or removed in VS 2026. The VSComponents DSC resource silently skipped them, so the Windows 11 SDK (26100) and WindowsAppSDK C# support never installed, breaking the build (cppwinrt / WindowsAppSDK failures). - Windows10SDK.22621/26100 -> Windows11SDK.22621/26100 (renamed in VS 2026) - ComponentGroup.WindowsAppSDK.Cs -> WindowsAppSdkSupport.CSharp; added WindowsAppSdkSupport.Cpp - Removed Windows10SDK.19041 (only a min-version floor) and Windows10SDK.20348 (unused, removed from VS 2026) - readme: correct '22621' SDK label from Windows 10 to Windows 11 Fixes #48778 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
1 participant
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.
Summary
Fixes #48778 — the automated developer setup (
winget configure .config\configuration.winget) provisions Visual Studio 2026 but feeds it a.vsconfigcontaining Visual Studio 2022-era component IDs that were renamed or removed in VS 2026. TheVSComponentsDSC resource silently skips the invalid IDs, so the Windows 11 SDK (26100) and WindowsAppSDK C# support never install — breaking the build with cppwinrt (exit code 3) and WindowsAppSDK target failures, exactly as reported.Root cause
PR #45534 bumped
.config/configuration.wingetfrom VS 2022 → VS 2026 (Microsoft.VisualStudio.Community,channelId: VisualStudio.18.Release) but left.vsconfiguntouched. Five component IDs in.vsconfigare invalid in the VS 2026 (Dev18) catalog:.vsconfig(old, VS 2022)Component.Windows10SDK.22621Component.Windows11SDK.22621Component.Windows10SDK.26100Component.Windows11SDK.26100(the build's target SDK)ComponentGroup.WindowsAppSDK.CsWindowsAppSdkSupport.CSharpComponent.Windows10SDK.19041WindowsTargetPlatformMinVersionfloor — never a real install requirement)Component.Windows10SDK.20348A single
.vsconfigis the source of truth for all three winget variants (configuration.winget,configuration.vsProfessional.winget,configuration.vsEnterprise.winget), which reference it via${WinGetConfigRoot}\..\.vsconfig, so this one edit fixes every automated path.Changes
Windows10SDK.22621/26100→Windows11SDK.22621/26100ComponentGroup.WindowsAppSDK.Cs→WindowsAppSdkSupport.CSharp, and addedWindowsAppSdkSupport.Cpp(PowerToys' C++/WinRT projects need it)Windows10SDK.19041andWindows10SDK.20348doc/devdocs/readme.md: corrected the10.0.22621.0SDK label from "Windows 10 SDK" to "Windows 11 SDK"Validation
vswhere -include packages— all present/valid..vsconfigparses as valid JSON.Cpp.Build.props(WindowsTargetPlatformVersion = 10.0.26100.0, min10.0.19041.0) andCommon.Dotnet.CsWinRT.props.Notes
The docs still list "VS 2022 17.4+" as an alternative; this
.vsconfigis aligned to the recommended/automated VS 2026 path. The VS Installer treats any unrecognized component IDs in.vsconfiggracefully (shown as unavailable, non-blocking) for VS 2022 users.