Add VS2026 platform toolset mapping#949
Merged
jasonsandlin merged 3 commits intomainfrom Mar 13, 2026
Merged
Conversation
jplafonta
approved these changes
Mar 13, 2026
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.
VS2026 uses VisualStudioVersion=18 which wasn't mapped in the GDK or Win32 props files, causing PlatformToolset to fall back to v100 and fail to build. This adds a mapping for VS2026 to use the v143 toolset (same as VS2022) in both libHttpClient.GDK.props and libHttpClient.Win32.props.
Also adds HCLibToolset mapping for the v145 platform toolset (VS2026 native). Without it, if a consumer project uses PlatformToolset=v145 with HCStaticLib=true, HCLibToolset falls back to $(PlatformToolsetVersion) which may not resolve correctly, causing the wrong static lib project name to be constructed. This is a forward-compat addition — it has zero impact on existing v141/v142/v143 consumers