Remove duplicate DNX guidance - #1530
Merged
David Pine (IEvangelist) merged 1 commit intoAug 18, 2026
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 32c349b4-907d-42e9-aad8-2f0edc267779
50 tasks
David Pine (IEvangelist)
marked this pull request as ready for review
August 18, 2026 14:14
Contributor
There was a problem hiding this comment.
Pull request overview
Removes duplicated documentation about Aspire CLI DNX delegation in the Aspire SDK “get started” guide, leaving “Running with dotnet run” as the single source of truth for invocation modes and related behavior.
Changes:
- Removed the duplicate “Delegating through DNX” section that repeated
Path/Dnx/DnxPinnedguidance. - Folded the key “DNX uses configured NuGet sources / restore failures fail explicitly” details into the existing
dotnet runnote.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
|
||
| :::note | ||
| `dotnet run` is noninteractive, so `dnx` restores and executes without prompting for confirmation. If `dnx` can't be found on `PATH` when `Dnx` or `DnxPinned` mode is configured, the build emits error `ASPIRE011`. Install or use the .NET SDK 10.0 or later, set `AspireCliInvocationMode` to `Path` to use the global `aspire` command, or set `AspireCliPath` to an explicit Aspire CLI executable. | ||
| `dotnet run` is noninteractive, so `dnx` restores and executes without prompting for confirmation and uses your configured NuGet sources. Restore or probe failures fail explicitly instead of falling back to an incomplete direct launch. If `dnx` can't be found on `PATH` when `Dnx` or `DnxPinned` mode is configured, the build emits error `ASPIRE011`. Install or use the .NET SDK 10.0 or later, set `AspireCliInvocationMode` to `Path` to use the global `aspire` command, or set `AspireCliPath` to an explicit Aspire CLI executable. |
Contributor
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
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.
Why
PR #1512 was merged after an automated
release/13.5conflict resolution retained both the existingRunning with dotnet runguidance and a secondDelegating through DNXsection. The two sections repeat thePath,Dnx, andDnxPinnedbehavior and configuration example.What changed
Delegating through DNXsection.Running with dotnet runsection as the single mode reference.Validation
pnpm --dir .\src\frontend run lintpnpm --dir .\src\frontend exec vitest run --config vitest.config.ts tests/unit/topic-resolver.vitest.test.ts tests/unit/seo-lengths.vitest.test.ts(15 passed)Related to #1512.