Add support for building tool packages with runtime identifier set without building RID-specific packages #51281
+43
−6
Conversation
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
…thout building RID-specific packages
baronfel
approved these changes
Oct 15, 2025
MiYanni
approved these changes
Oct 15, 2025
|
Daniel and I chatted more and we don't think my idea would work/be that much more usable. So this is good. When we get Tactics approval we'll need to go update the breaking change notice for RID specific Tools. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Fixes #51199
Now that we support RID-specific tool packages, setting a
RuntimeIdentifierfor a project withPackAsToolset to true will create a RID-specific tool package without a primary package. With this PR, you will be able to restore the previous behavior by setting the following properties: