Clarify global.json paths feature limitations for SDK-only scenarios #47624
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
global.json"paths" feature documentation was missing important clarification about when it applies, which could lead to user confusion when the feature doesn't work as expected in certain scenarios.Problem
Users might expect the "paths" feature to affect all .NET application launch methods, but it only works with .NET SDK commands. The documentation didn't clearly state this limitation, potentially causing confusion when users try to use custom SDK paths with:
app.exe)dotnet app.dll)dotnet exec app.dll)Solution
Added a clear note in the "paths" section explaining:
dotnet rundotnet app.dll, ordotnet exec app.dllChanges
pathssection indocs/core/tools/global-json.md.gitignoreto exclude npm artifactsThe change is minimal and surgical, preserving all existing content while adding essential clarification for users.
Fixes #[issue-number]
This pull request was created as a result of the following prompt from Copilot chat.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.
Internal previews