[release/3.1] Target 3.1.0 shared framework in global tools

[dougbu]

• Required dependencies are not listed #19108
• ensure the packaged runtimeconfig.json file uses the 3.1.0 shared framework
  • disable $(TargetLatestDotNetRuntime) in tool projects
  • skip @(FrameworkReference) item update if $(TargetLatestDotNetRuntime) is disabled

nit: Move $(PackAsTool) settings together

---

Description

In 3.1.x servicing, the global tools shipped from the dotnet/aspnetcore repo had an undeclared dependency on the latest shared framework. Installing, say, the 3.1.9 version of dotnet-sql-cache went fine. But, attempts to run it fail with the output below unless the 3.1.9 shared framework was available.

> dotnet-sql-cache
It was not possible to find any compatible framework version
The framework 'Microsoft.NETCore.App', version '3.1.9' was not found.
  - The following frameworks were found:
      2.1.21 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
      3.1.7 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
      5.0.0-rc.2.20475.5 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

You can resolve the problem by installing the specified framework and/or SDK.

The specified framework can be found at:
  - https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=3.1.9&arch=x64&rid=win10-x64

Customer Impact

From 3.1.11 forward, customers will be able to install the latest global tools from dotnet/aspnetcore without also updating their installed shared frameworks.

Regression?

Yes but from way back in 2.1.x. Those tools worked fine because, though the runtimeconfig.json files we shipped referenced the latest version of Microsoft.NETCore.App, that package could be resolved when the tool was installed.

Risk (see taxonomy)

Incredibly small. The only possible risk would be a tool we ship from dotnet/aspnetcore depending on a fix in a serviced shared framework assembly. Such a dependency could be considered a breaking change and should be avoided.

Original issue and/or the PR to master.

• Required dependencies are not listed #19108 is the (customer-reported) issue
• [master] Target 6.0.0 shared framework in global tools in servicing #27600 is the PR for master

Packaging impact? (if a libraries change)

None

[dougbu]

Will add ask mode template shortly&hellip:

[dougbu]

Blocked until branch is open