Skip to content

Commit bd82a27

Browse files
Copilotelinor-fung
andcommitted
Update text as suggested by @elinor-fung and move sentence position
Co-authored-by: elinor-fung <[email protected]>
1 parent 7239180 commit bd82a27

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/core/tools/global-json.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,10 +93,10 @@ The following table shows the possible values for the `rollForward` key:
9393

9494
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.
9595

96-
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.
97-
9896
These paths are searched in the order they're defined and the first [matching](#matching-rules) SDK is used.
9997

98+
This feature enables using local SDK installations (such as SDKs relative to a repository root or placed in a custom folder) that are not installed globally on the system.
99+
100100
> 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`.
101101
102102
#### errorMessage

0 commit comments

Comments
 (0)