Open
Breaking change: Document dnx scripts bypassing global.json SDK selection#54645
Conversation
3 tasks
Copilot
AI
changed the title
[WIP] Update dnx scripts to use the newest SDK
Breaking change: Document dnx scripts bypassing global.json SDK selection
Jul 5, 2026
gewarren
reviewed
Jul 6, 2026
| @@ -0,0 +1,42 @@ | |||
| --- | |||
| title: "Breaking change: dnx scripts bypass global.json SDK selection" | |||
| description: "Learn about the breaking change in .NET 10 SDK 10.0.302 where the dnx and dnx.cmd scripts no longer respect global.json for SDK selection." | |||
Collaborator
There was a problem hiding this comment.
Suggested change
| description: "Learn about the breaking change in .NET 10 SDK 10.0.302 where the dnx and dnx.cmd scripts no longer respect global.json for SDK selection." | |
| description: "Learn about the breaking change in .NET 11 where the dnx and dnx.cmd scripts no longer respect global.json for SDK selection." |
Collaborator
|
@copilot Please respond to feedback |
Contributor
Author
All feedback addressed in commit
|
gewarren
approved these changes
Jul 6, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Documents a breaking behavioral change in the dnx/dnx.cmd installer scripts: they now select and invoke the newest installed SDK directly (bypassing global.json SDK selection), and provides a workaround (dotnet dnx) for muxer-based selection.
Changes:
- Added a new breaking change article describing previous behavior, new behavior, rationale, and recommended action.
- Updated .NET 10 and .NET 11 compatibility indexes to include the new breaking change entry.
- Updated the compatibility TOC and the
dotnet tool execdocs to reference/describednx.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/core/tools/dotnet-tool-exec.md | Updates the dnx script description under dotnet tool exec. |
| docs/core/compatibility/toc.yml | Adds the breaking change entry under the compatibility TOC. |
| docs/core/compatibility/sdk/11/dnx-scripts-bypass-global-json.md | New breaking change article explaining the dnx script behavior change and workaround. |
| docs/core/compatibility/11.md | Adds the breaking change link to the .NET 11 compatibility index. |
| docs/core/compatibility/10.md | Adds the breaking change link to the .NET 10 compatibility index. |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
gewarren
reviewed
Jul 6, 2026
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.
The
dnx/dnx.cmdscripts were updated to always invoke the newest installed SDK (viadotnet --list-sdks) rather than going through the .NET muxer, which meansglobal.jsonSDK pinning is now ignored. This broke users who had pre-.NET 10 SDKs pinned, getting crypticUnrecognized command or argument 'execute'errors.Changes
docs/core/compatibility/sdk/10.0/dnx-scripts-bypass-global-json.md— covers previous/new behavior, reason (version-independent commands should always use newest SDK), and workaround (dotnet dnxto restore muxer-based selection)docs/core/compatibility/10.md— added SDK section entrydocs/core/compatibility/toc.yml— added TOC entry alongside existingdnx.ps1articledocs/core/tools/dotnet-tool-exec.md— updateddnxscript description to document the bypass behavior and point users todotnet dnxfor the old behaviorVersions affected: .NET 10 SDK 10.0.302, 10.0.400, .NET 11 Preview 6.
Internal previews