Skip to content

[docs] Document CLI bundle default for C# AppHost templates - #2137

Open
aspire-repo-bot[bot] wants to merge 2 commits into
release/17.0from
docs/pr-21986-43318329721-1-c3344af53690e7d8
Open

aspire-repo-bot[bot] wants to merge 2 commits into
release/17.0from
docs/pr-21986-43318329721-1-c3344af53690e7d8

Conversation

@aspire-repo-bot

Copy link
Copy Markdown
Contributor

Documents changes from microsoft/aspire#21986

Author: @DamianEdwards (PR author per source PR; please verify)

Target branch: Targeting release/17.0 — the latest release branch on microsoft/aspire.dev — because release/17.1 (from the source PR milestone 17.1) does not exist there.

Why: The source PR removes the redundant AspireUseCliBundle opt-in from project/single-file templates and aspire init, since current SDKs enable the CLI bundle by default. CLI generation still emits it for SDK versions before 17.0 and 17.0.0 prereleases. An inherited AspireUseCliBundle=false now takes effect and the SDK reports ASPIRE013. Signals: project_template_changed, cli_command_file_changed, pr_body_has_cli_flag_mention.

Changes (updated page):

  • src/frontend/src/content/docs/get-started/aspire-sdk.mdx: updated the CLI bundle section to describe the new default and templates behavior.

SME should confirm the ASPIRE013 wording and whether the ASPIRE010 page needs further changes.

Generated by PR Documentation Check for #21986 · copilot · auto · 27.3 AIC · ⌖ 1.26 AIC · ⊞ 7.4K · ◷

@aspire-repo-bot aspire-repo-bot Bot added the docs-from-code Copilot initiated issue from dotnet/aspire repo label Nov 12, 2026
@aspire-repo-bot

Copy link
Copy Markdown
Contributor Author

Frontend HTML artifact ready

The latest frontend build uploaded the frontend-dist artifact for PR #2137. Use the VS Code button below to open this PR with GitHub Artifacts Explorer and browse the built HTML locally.

VS Code: Open PR #2137 artifacts

This comment updates automatically when a new frontend build artifact is uploaded.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@eerhardt
Eric Erhardt (eerhardt) marked this pull request as ready for review November 12, 2026 23:35
Copilot AI balanced review requested due to automatic review settings November 12, 2026 23:35

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The documentation incorrectly recommends disabling AspireUseCliBundle, which causes current C# AppHosts to fail with ASPIRE013 rather than use a NuGet fallback.

1 open issue
What changed in this PR

Updates the Aspire SDK getting-started documentation to describe the CLI bundle as enabled by default for current C# AppHost SDKs.

Changes:

  • Replaces the previous opt-in guidance with default-enabled behavior.
  • Revises guidance for disabling the bundle and enabling it on older SDKs.
File Description
src/​frontend/​src/​content/​docs/​get-started/​aspire-sdk.mdx Updates the CLI bundle default and configuration guidance.

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.
Current C# AppHost SDKs default `AspireUseCliBundle` to `true`, enabling the bundle without an explicit project setting. Set it to `false` to use NuGet-restored orchestration dependencies; this reports warning [`ASPIRE010`](/diagnostics/aspire010/). On older SDKs, set it to `true` to enable the bundle.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-from-code Copilot initiated issue from dotnet/aspire repo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants