Add how-to: Test prerelease .NET SDKs locally with global.json paths#52893
Merged
jfversluis merged 7 commits intodotnet:mainfrom Apr 9, 2026
Merged
Add how-to: Test prerelease .NET SDKs locally with global.json paths#52893jfversluis merged 7 commits intodotnet:mainfrom
jfversluis merged 7 commits intodotnet:mainfrom
Conversation
…n paths This adds a step-by-step how-to guide for using the sdk.paths property in global.json (new in .NET 10) to install and test prerelease SDKs in a project-local directory without modifying system-wide installations. The article covers: - Installing a prerelease SDK with dotnet-install scripts - Configuring global.json with the paths property - Installing workloads (MAUI, wasm-tools) on the local SDK - Team convenience scripts for cross-platform onboarding - CI integration with GitHub Actions - Cleanup and limitations Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ate cleanup - Explain 'host' as the system-wide dotnet installation on first mention - Remove all ./.dotnet/dotnet fallback instructions after prerequisites - Simplify workload section to use plain dotnet commands - Replace duplicate 'Undo all changes' section with link to Clean up - Add brief mention that paths supports multiple entries - Remove redundant IMPORTANT callout from quick start section - Convert quick start intro from TIP callout to plain text Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…h dotnet --info Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Workload commands (install, list) store metadata relative to the dotnet root of the host process. When using the system host with sdk.paths, workloads end up in the system installation rather than the local one. This is a known gap (dotnet/sdk#49825). Updated all workload examples to use ./.dotnet/dotnet directly, with an IMPORTANT callout explaining why and linking to the tracking issue. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new how-to article that walks you through using global.json sdk.paths (introduced in .NET 10) to test a prerelease SDK from a project-local install, and links the new article from the tools/diagnostics TOC.
Changes:
- Adds
docs/core/tools/test-prerelease-sdk-locally.mdwith end-to-end instructions (local install,global.jsonsetup, workloads, CI, cleanup). - Updates
docs/navigate/tools-diagnostics/toc.ymlto include the new article under .NET SDK.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
docs/core/tools/test-prerelease-sdk-locally.md |
New how-to article documenting local prerelease SDK testing via global.json sdk.paths. |
docs/navigate/tools-diagnostics/toc.yml |
Adds navigation entry pointing to the new how-to article. |
- Add ai-usage: ai-assisted to front matter - Fix missing space and clarify PATH behavior (session-only, not permanent) - Reword prerequisite to avoid mixing SDK/host terminology - Fix inconsistent tab title: 'Windows PowerShell' -> 'Windows (PowerShell)' Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Apr 8, 2026
gewarren
approved these changes
Apr 8, 2026
- Apply wording suggestions (parentheses style, 'how-to article', remove 'Note that') - Add backticks to PATH in Limitations section - Use 'might' instead of 'may' per style guide - Convert team install scripts to tabbed layout (macOS/Linux + Windows tabs) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds a new how-to article explaining how to use the
sdk.pathsproperty inglobal.json(new in .NET 10) to install and test prerelease SDKs in a project-local directory without modifying system-wide installations.What's covered
dotnet-installscriptsglobal.jsonwith thepathsproperty and$host$fallbackPlacement
docs/core/tools/test-prerelease-sdk-locally.mddocs/navigate/tools-diagnostics/toc.yml, right after the existing "global.json overview" entryNotes
global.jsonoverview page already documents thepathsanderrorMessageproperties briefly. This article provides a full end-to-end tutorial./cc @dotnet/docs
Internal previews