[release/10.0.1xx-preview6] Add dnx support
#49488
Merged
Conversation
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
… something. This won't allow those commands to show up in subcommand-help of their parents, however.
dnx supportdnx support
baronfel
approved these changes
Jun 19, 2025
ad772df
into
dotnet:release/10.0.1xx-preview6
32 of 33 checks passed
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.
Backport of #49425 and #49461 to .NET 10 Preview 6.
Customer Impact
This adds support for direct tool execution with
dnxas described in this design: dotnet tool exec and dnxSupport for
dotnet tool execis already in preview 6, this adds thednxscripts as a shorter / simpler way to invoke .NET Tools.The direct impact is that you will be able to run (for example)
dnx powershellinstead ofdotnet tool exec powershell.Regression
No, this is new feature work that we are adding for .NET 10
Testing
Manual testing
Risk
Low, this change adds new functionality but shouldn't change existing behavior.