Repository navigation
[docs] Document ASPIRE013 and scope ASPIRE010 to non-C# AppHosts - #2071
Merged
Sébastien Ros (sebastienros) merged 6 commits intoNov 13, 2026
Merged
Sébastien Ros (sebastienros) merged 6 commits into
Sébastien Ros (sebastienros) merged 6 commits into
Conversation
4 of 14 tasks
David Pine (IEvangelist)
self-requested a review
November 13, 2026 14:54
David Pine (IEvangelist)
marked this pull request as ready for review
November 13, 2026 14:54
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The SDK documentation still describes an obsolete opt-in configuration, contradicting the mandatory C# bundle requirement and ASPIRE013 guidance and misleading users about which configurations remain valid.
1 open issue
What changed in this PR
Updates Aspire diagnostic documentation for the C# CLI-bundle requirement introduced by microsoft/aspire#21288, targeting release 17.0.
Changes:
- Adds ASPIRE013 documentation for the unsuppressible C# AppHost error.
- Scopes ASPIRE010 to non-C# AppHosts and updates ASPIRE009 recovery guidance.
- Adds ASPIRE013 to the diagnostics index and updates the SDK guide.
| File | Description |
|---|---|
src/frontend/src/content/docs/get-started/aspire-sdk.mdx |
Describes language-specific CLI-bundle requirements. |
src/frontend/src/content/docs/diagnostics/overview.mdx |
Lists ASPIRE013 as an error. |
src/frontend/src/content/docs/diagnostics/aspire013.mdx |
Adds error details, an example, and corrective steps. |
src/frontend/src/content/docs/diagnostics/aspire010.mdx |
Limits the warning and examples to non-C# AppHosts. |
src/frontend/src/content/docs/diagnostics/aspire009.mdx |
Distinguishes bundle-resolution remedies by AppHost language. |
Review effort: Balanced
| When it uses the Aspire CLI bundle, those binaries update when you update the Aspire CLI through [`aspire update --self`](/reference/cli/commands/aspire-update/). Without the bundle, the Aspire SDK version used by the AppHost determines the binaries by adding implicit references to the RID-specific `Aspire.Hosting.Orchestration.*` and `Aspire.Dashboard.Sdk.*` packages. | ||
|
|
||
| New C# AppHost projects created with `aspire new` or `dotnet new`, and new single-file AppHosts created with `aspire init`, set `AspireUseCliBundle` to `true` automatically. For existing AppHosts, set `AspireUseCliBundle` to `true` to enable the CLI bundle. We recommend enabling it now because the CLI bundle will become the only supported source for orchestration dependencies in an upcoming Aspire release. The SDK property currently defaults to `false`, so launching a C# AppHost with `dotnet run` or an IDE continues to work without requiring the Aspire CLI. Leaving it unset (or explicitly `false`) reports warning [`ASPIRE010`](/diagnostics/aspire010/) as a reminder that some Aspire features require the bundle; suppress it if you intend to keep using NuGet-restored orchestration dependencies. | ||
| New C# AppHost projects created with `aspire new` or `dotnet new`, and new single-file AppHosts created with `aspire init`, set `AspireUseCliBundle` to `true` automatically. For existing AppHosts, set `AspireUseCliBundle` to `true` to enable the CLI bundle. We recommend enabling it now because the CLI bundle will become the only supported source for orchestration dependencies in an upcoming Aspire release. The SDK property currently defaults to `false`, so launching a C# AppHost with `dotnet run` or an IDE continues to work without requiring the Aspire CLI. C# AppHosts require the CLI bundle, so setting `AspireUseCliBundle` to `false` reports error [`ASPIRE013`](/diagnostics/aspire013/), and suppressing `ASPIRE013` doesn't bypass the requirement. Non-C# AppHosts that set it to `false` report the suppressible warning [`ASPIRE010`](/diagnostics/aspire010/). |
- C# AppHosts default AspireUseCliBundle to true and can't opt out (ASPIRE013) - Non-C# AppHosts default to false, so ASPIRE010 also fires when unset - Use a realistic .fsproj file name in ASPIRE010 examples - Register the ASPIRE013 page in the diagnostics sidebar (fixes the build)
Sébastien Ros (sebastienros)
enabled auto-merge (squash)
November 13, 2026 22:49
Contributor
Author
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
The unknown-arguments example ran 'aspire destroy --force' in a bash block, which the pipeline command options unit test flags as an undocumented option. Describe the invalid option in prose and keep the error output.
Sébastien Ros (sebastienros)
requested a review
from Mitch Denny (mitchdenny)
as a code owner
November 13, 2026 23:28
Sébastien Ros (sebastienros)
deleted the
docs/pr-21288-42166733916-1-375b5dd597b8e0d3
branch
November 13, 2026 23:55
This was referenced Nov 16, 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.

Documents changes from microsoft/aspire#21288 by
@IEvangelist-triggeredrun (PR author per source PR).Targeting
release/17.0based on the source PR milestone17.0(exact match).Why
The source PR restores ASPIRE010 as the suppressible warning for non-C# AppHosts that opt out of the CLI bundle, and introduces ASPIRE013 as the unsuppressible error for C# AppHosts. Signals:
diagnostic_documentation_changed,pr_body_has_cli_flag_mention,pr_body_has_user_facing_section.Changes
diagnostics/aspire013.mdxdiagnostics/aspire010.mdx(non-C# scope, mutually exclusive with ASPIRE013),diagnostics/overview.mdx(ASPIRE013 row),diagnostics/aspire009.mdx,get-started/aspire-sdk.mdxThe ASPIRE013 "Version introduced" badge is set to 17.0 (target branch); SME please confirm.