Skip to content

Add workaround for RID-specific tool publishing #49295

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Add workaround for RID-specific tool publishing #49295

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
669732e
Initial plan
Copilot Oct 16, 2025
c2e534d
Add workaround for maintaining old tool behavior with RuntimeIdentifier
Copilot Oct 17, 2025
1b4ce51
Update docs/core/compatibility/sdk/10.0/dotnet-tool-pack-publish.md
gewarren Oct 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/core/compatibility/sdk/10.0/dotnet-tool-pack-publish.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,15 @@ This change enables the creation of optimized, platform-specific .NET Tool packa

If you want to create tools for only a subset of platforms, use `ToolPackageRuntimeIdentifiers`. If you want to disable RID-specific tool packages entirely, you should conditionally include or exclude the `RuntimeIdentifiers` property in your project file.

Alternatively, if you want to maintain the previous behavior (framework-dependent, platform-agnostic .NET Tools) even when a `RuntimeIdentifier` is specified, add the following properties to your project file:

```xml
<PropertyGroup>
<CreateRidSpecificToolPackages>false</CreateRidSpecificToolPackages>
<UseAppHost>false</UseAppHost>
</PropertyGroup>
```

## Affected APIs

None.
Loading