Skip to content

Add local SDK clarification to global.json paths documentation #47673

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

Merged
merged 4 commits into from
Aug 4, 2025
Merged

Add local SDK clarification to global.json paths documentation #47673

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
0f32b01
Initial plan
Copilot Jul 30, 2025
7239180
Add local SDK clarification to global.json paths documentation
Copilot Jul 30, 2025
bd82a27
Update text as suggested by @elinor-fung and move sentence position
Copilot Jul 30, 2025
f76a251
Replace 'are not' with 'aren't' in local SDK documentation
Copilot Aug 4, 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
2 changes: 2 additions & 0 deletions docs/core/tools/global-json.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,8 @@ The following table shows the possible values for the `rollForward` key:

Specifies the locations that should be considered when searching for a compatible .NET SDK. Paths can be absolute or relative to the location of the *global.json* file. The special value `$host$` represents the location corresponding to the running `dotnet` executable.

This feature enables using local SDK installations (such as SDKs checked into a repository or placed in a custom folder) that are not installed globally on the system.

These paths are searched in the order they're defined and the first [matching](#matching-rules) SDK is used.

> The "paths" feature only works when using commands that engage the .NET SDK, such as `dotnet run`. It does NOT affect scenarios such as running the native apphost launcher (`app.exe`), running with `dotnet app.dll`, or running with `dotnet exec app.dll`. To use the "paths" feature, you must use SDK commands like `dotnet run`.
Expand Down
Loading