Add local SDK clarification to global.json paths documentation #47673
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.
This PR updates the documentation for the
global.json
paths
property to explicitly mention that this feature enables using local SDK installations.The current documentation explains what the
paths
property does technically, but doesn't clearly communicate one of its key use cases: enabling the use of SDKs that are not installed globally on the system.cc @dotnet/appmodel @richlander
Changes Made
Added a clarifying sentence to the
paths
property description indocs/core/tools/global-json.md
:The sentence is positioned after the explanation of how paths are searched, providing logical flow from the technical details to the practical use case.
Impact
This change will help users who are searching for information about how to use local SDKs find this feature more easily. The existing example already demonstrates this concept with the
.dotnet
path, but the description now makes this use case explicit.The change is minimal and focused, adding only one sentence without modifying any existing content or functionality.
This pull request was created as a result of the following prompt from Copilot chat.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.
Internal previews