Merged
Conversation
dlemstra
approved these changes
Feb 1, 2026
mcumming
approved these changes
Feb 2, 2026
erdembayar
approved these changes
Feb 2, 2026
This was referenced Feb 9, 2026
This was referenced Feb 24, 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
4 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.
Resolve #978
A breaking change in .NET 10 SDK is that .NET tool packages are now RID-specific. As a result, primary assets within the package are now under a
win-x64folder instead of ananyfolder. However, the build still put Windows SDK tools under theanyfolder. As a result, at runtime this tool (underwin-x64) could not find Windows SDK tool files in atoolssubdirectory.The fix is to put the Windows SDK tools under the
win-x64folder instead of theanyfolder.This is a packaging-specific regression. As part of the build, a package verification script verifies that Windows SDK tools are in the expected location succeeded because it continued verifying the old location: the
anyfolder.This change also updates the verification script to look for both sign.dll and Windows SDK tools in the
win-x64folder.