Add workaround for RID-specific tool publishing

[Copilot]

This PR adds documentation for a workaround that allows users to maintain the old behavior (framework-dependent, platform-agnostic .NET Tools) when they have a RuntimeIdentifier specified in their project file.

Context

In .NET 10, the tool packaging process changed to use RuntimeIdentifiers to create platform-specific tool packages. While this enables optimized scenarios like self-contained and trimmed tools, some users need to maintain the previous behavior where tools were framework-dependent and platform-agnostic.

Changes

Added a workaround to the "Recommended action" section of the breaking change article that explains users can opt out of the new behavior by setting two properties in their project file:

<PropertyGroup>
  <CreateRidSpecificToolPackages>false</CreateRidSpecificToolPackages>
  <UseAppHost>false</UseAppHost>
</PropertyGroup>

This workaround was introduced in dotnet/sdk#51281 and requires the .NET 10.0.100 GA SDK or later.

Fixes #47916

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add new workaround for RID-specific tool publishing</issue_title>
<issue_description>### Type of issue

Typo

Description

In dotnet/sdk#51281 we added a way for users that were making .NET Tools that had a RuntimeIdentifier specified to get the same behavior they had on .NET 9 and below - that is, making framework-dependent, platform-agnostic .NET Tools.

To do so, the following project properties need to be added, and the 10.0.100 GA release of the .NET SDK must be used.

    <CreateRidSpecificToolPackages>false</CreateRidSpecificToolPackages>
    <UseAppHost>false</UseAppHost>

[Enter feedback here]

Page URL

https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/10.0/dotnet-tool-pack-publish

Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/compatibility/sdk/10.0/dotnet-tool-pack-publish.md

Document Version Independent Id

8eb98a02-7d87-9fd4-0429-c5f059e8f27b

Platform Id

32c3d15f-5b4b-a175-e761-6d7b0754db1a

Article author

@gewarren

Metadata

• ID: 62f68c53-02c5-451d-fc2c-453fcef7aa87
• PlatformId: 32c3d15f-5b4b-a175-e761-6d7b0754db1a
• Service: dotnet-fundamentals

Related Issues</issue_description>

Comments on the Issue (you are @copilot in this section)

Fixes #49289

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

---

Internal previews

📄 File	🔗 Preview link
docs/core/compatibility/sdk/10.0/dotnet-tool-pack-publish.md	.NET tool packaging creates RuntimeIdentifier-specific tool packages

[Copilot]

Pull Request Overview

This PR documents a workaround that allows developers to opt out of the new .NET 10 RID-specific tool packaging behavior and maintain framework-dependent, platform-agnostic tools when a RuntimeIdentifier is specified.

Key Changes:

• Added documentation for two MSBuild properties (CreateRidSpecificToolPackages and UseAppHost) that restore pre-.NET 10 tool packaging behavior
• Provides an alternative solution for users who need the old behavior despite having a RuntimeIdentifier in their project

[gewarren]

@baronfel I guess we should wait until GA to merge this?

[baronfel]

@gewarren if possible that would be great - though I know it can be annoying to babysit a stack of PRs for an extended period of time.

[BillWagner]

This LGTM.