Update global.json #117460
Update global.json #117460
Conversation
Use the new paths feature and allow newer SDKs when building https://learn.microsoft.com/en-us/dotnet/core/tools/global-json#paths
There was a problem hiding this comment.
Pull Request Overview
This PR enhances the global.json for SDK lookup flexibility by introducing the new paths feature, allowing SDK roll-forward on major versions, and providing a custom error message when the required SDK is missing.
- Added
"paths"array to include local.dotnetfolder and$host$placeholder. - Kept
"rollForward": "major"to permit newer SDKs. - Included
"errorMessage"to guide developers to the install script.
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
|
Can we remove the dotnet.cmd/sh helper when 10.0 releases and the feature is GA? |
|
Yes, when VS supports it fully :) |
|
Note: won’t help for runtime execution. It’s an sdk only feature. We might want to keep the scripts around if someone needs to run a tool on the latest |
|
(Also ‘dnvm restore’ will just install the sdk locally so you don’t have to worry about this). |
|
Right but I would still want to replace these scripts eventually with the eng/common/dotnet.cmd/sh scripts that we now have. |
|
The WasmBuildTests failures are related |
Use the new paths feature and allow newer SDKs when building
https://learn.microsoft.com/en-us/dotnet/core/tools/global-json#paths