Use dnx instead of dotnet tool exec in MCP server template README #6571
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
stephentoub
approved these changes
Jul 2, 2025
timheuer
approved these changes
Jul 2, 2025
joperezr
pushed a commit
that referenced
this pull request
Jul 8, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Related to #6518.
I spoke to @baronfel about this.
dnxis the preferred syntax and is reminiscent ofnpx. I believe this will also provide a preferred failure mode on an old .NET SDK (OS command not found vs. dotnet giving an unhandledargserror).We will provide the
dnxsyntax on NuGet.org for the copy-paste VS Code config and I will prescribednxwhile I add NuGet support to the MCP Registry.Apologies for not getting this into the other PR: #6547
I am open to feedback.