From eda6010eb2beedcc6e16a3f78b5901559508a939 Mon Sep 17 00:00:00 2001
From: "aspire-repo-bot[bot]"
<268009190+aspire-repo-bot[bot]@users.noreply.github.com>
Date: Fri, 6 Nov 2026 05:14:56 +0000
Subject: [PATCH 1/3] Document ASPIRE013 and restore ASPIRE010 scope
---
.../content/docs/diagnostics/aspire009.mdx | 2 +-
.../content/docs/diagnostics/aspire010.mdx | 16 +++----
.../content/docs/diagnostics/aspire013.mdx | 42 +++++++++++++++++++
.../src/content/docs/diagnostics/overview.mdx | 1 +
.../content/docs/get-started/aspire-sdk.mdx | 2 +-
5 files changed, 53 insertions(+), 10 deletions(-)
create mode 100644 src/frontend/src/content/docs/diagnostics/aspire013.mdx
diff --git a/src/frontend/src/content/docs/diagnostics/aspire009.mdx b/src/frontend/src/content/docs/diagnostics/aspire009.mdx
index ead015d026..25625f8e42 100644
--- a/src/frontend/src/content/docs/diagnostics/aspire009.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspire009.mdx
@@ -50,6 +50,6 @@ When no explicit path is set, either [install the Aspire CLI](https://get.aspire
If `Dnx` or `DnxPinned` mode can't find `dnx`, the run preflight reports [`ASPIRE011`](/diagnostics/aspire011/). A missing `dnx` command isn't itself an `ASPIRE009` condition, although a separate bundle-resolution failure can still produce `ASPIRE009`.
-Alternatively, set `AspireUseCliBundle` to `false` to restore orchestration dependencies from NuGet packages. Doing so reports [`ASPIRE010`](/diagnostics/aspire010/) because some Aspire features require the CLI bundle.
+C# AppHosts require the CLI bundle, and setting `AspireUseCliBundle` to `false` reports [`ASPIRE013`](/diagnostics/aspire013/). Non-C# AppHosts can set it to `false` to restore orchestration dependencies from NuGet packages, which reports the suppressible warning [`ASPIRE010`](/diagnostics/aspire010/).
For more information, see [Use the Aspire CLI bundle for orchestration dependencies](/get-started/aspire-sdk/#use-the-aspire-cli-bundle-for-orchestration-dependencies).
diff --git a/src/frontend/src/content/docs/diagnostics/aspire010.mdx b/src/frontend/src/content/docs/diagnostics/aspire010.mdx
index f99552d710..5dd9ac3811 100644
--- a/src/frontend/src/content/docs/diagnostics/aspire010.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspire010.mdx
@@ -1,7 +1,7 @@
---
title: Compiler Warning ASPIRE010
seoTitle: 'ASPIRE010: Aspire CLI bundle opt-out warning · Aspire'
-description: Learn what causes Aspire compiler warning ASPIRE010 — the AppHost has opted out of the Aspire CLI bundle — and how to enable or suppress it.
+description: Learn what causes Aspire compiler warning ASPIRE010 — a non-C# AppHost has opted out of the Aspire CLI bundle — and how to enable or suppress it.
---
import { Badge } from '@astrojs/starlight/components';
@@ -15,25 +15,25 @@ import { Badge } from '@astrojs/starlight/components';
> '[ProjectName]' is configured with AspireUseCliBundle=false. Some Aspire features require the Aspire CLI bundle. Set AspireUseCliBundle=true to enable those features, or suppress ASPIRE010 to continue without the bundle. See https://aka.ms/aspire/diagnostics/aspire010 for more information.
-This diagnostic warning is reported when an AppHost project has `AspireUseCliBundle` set to `false` (the default). Launching the AppHost directly with `dotnet run` or an IDE continues to work without the Aspire CLI, but features that depend on the CLI bundle — such as resolving DCP and the Aspire Dashboard from the installed Aspire CLI instead of NuGet packages — remain unavailable.
+This diagnostic warning is reported when a non-C# AppHost project has `AspireUseCliBundle` explicitly set to `false`. Features that depend on the CLI bundle — such as resolving DCP and the Aspire Dashboard from the installed Aspire CLI instead of NuGet packages — remain unavailable.
+
+C# AppHosts require the CLI bundle and report error [`ASPIRE013`](/diagnostics/aspire013/) instead. The two diagnostics are mutually exclusive.
## Example
-The following configuration produces `ASPIRE010`:
+The following configuration in a non-C# AppHost produces `ASPIRE010`:
-```xml title="MyApp.AppHost.csproj"
+```xml title="MyApp.AppHost.proj"
false
```
-`ASPIRE010` is also reported when `AspireUseCliBundle` isn't set at all, because `false` is the default.
-
## To correct this warning
Set `AspireUseCliBundle` to `true` to opt in to CLI bundle delegation:
-```xml title="MyApp.AppHost.csproj"
+```xml title="MyApp.AppHost.proj"
true
@@ -45,7 +45,7 @@ An unresolved bundle layout reports [`ASPIRE009`](/diagnostics/aspire009/). [`AS
If you intend to keep using NuGet-restored orchestration dependencies, suppress `ASPIRE010`:
-```xml title="MyApp.AppHost.csproj"
+```xml title="MyApp.AppHost.proj"
false
$(NoWarn);ASPIRE010
diff --git a/src/frontend/src/content/docs/diagnostics/aspire013.mdx b/src/frontend/src/content/docs/diagnostics/aspire013.mdx
new file mode 100644
index 0000000000..f49aab2783
--- /dev/null
+++ b/src/frontend/src/content/docs/diagnostics/aspire013.mdx
@@ -0,0 +1,42 @@
+---
+title: Compiler Error ASPIRE013
+seoTitle: 'ASPIRE013: Aspire CLI bundle required · Aspire'
+description: Learn what causes Aspire compiler error ASPIRE013 when a C# AppHost disables the required Aspire CLI bundle, and how to correct it.
+---
+
+import { Badge } from '@astrojs/starlight/components';
+
+
+
+> '[ProjectName]' requires the Aspire CLI bundle. Remove AspireUseCliBundle or set it to true, and install the matching Aspire CLI from https://get.aspire.dev. ASPIRE013 cannot be suppressed to disable the bundle. See https://aka.ms/aspire/diagnostics/aspire013 for more information.
+
+This diagnostic error is reported when a C# AppHost project has `AspireUseCliBundle` set to anything other than `true`. The CLI bundle is required for C# AppHosts. Adding `ASPIRE013` (or [`ASPIRE010`](/diagnostics/aspire010/)) to `NoWarn` doesn't bypass the requirement.
+
+Non-C# AppHosts that opt out of the bundle report the suppressible warning [`ASPIRE010`](/diagnostics/aspire010/) instead. The two diagnostics are mutually exclusive.
+
+## Example
+
+The following configuration produces `ASPIRE013`:
+
+```xml title="MyApp.AppHost.csproj"
+
+ false
+
+```
+
+## To correct this error
+
+Remove the `AspireUseCliBundle` property, or set it to `true`, and install the matching Aspire CLI from [get.aspire.dev](https://get.aspire.dev):
+
+```xml title="MyApp.AppHost.csproj"
+
+ true
+
+```
+
+For more information, see [Use the Aspire CLI bundle for orchestration dependencies](/get-started/aspire-sdk/#use-the-aspire-cli-bundle-for-orchestration-dependencies).
diff --git a/src/frontend/src/content/docs/diagnostics/overview.mdx b/src/frontend/src/content/docs/diagnostics/overview.mdx
index 948812a0a6..742f2bd957 100644
--- a/src/frontend/src/content/docs/diagnostics/overview.mdx
+++ b/src/frontend/src/content/docs/diagnostics/overview.mdx
@@ -20,6 +20,7 @@ The following table lists the possible MSBuild and analyzer warnings and errors
| [ASPIRE009](/diagnostics/aspire009/) | Error | 'Project' is configured to use the Aspire CLI bundle, but the bundle could not be resolved. |
| [ASPIRE010](/diagnostics/aspire010/) | Warning | 'Project' is configured with AspireUseCliBundle=false. Some Aspire features require the Aspire CLI bundle. |
| [ASPIRE011](/diagnostics/aspire011/) | Error | 'Project' is configured to invoke the Aspire CLI through DNX, but the dnx command could not be found on PATH. |
+| [ASPIRE013](/diagnostics/aspire013/) | Error | 'Project' requires the Aspire CLI bundle. Remove AspireUseCliBundle or set it to true. |
| [ASPIREACADOMAINS001](/diagnostics/aspireacadomains001/) | (Experimental) Error | is for evaluation purposes only and is subject to change or removal in future updates. |
| [ASPIREACAEXPRESS001](/diagnostics/aspireacaexpress001/) | (Experimental) Error | is for evaluation purposes only and is subject to change or removal in future updates. |
| [ASPIREACANAMING001](/diagnostics/aspireacanaming001/) | (Experimental) Warning | is for evaluation purposes only and is subject to change or removal in future updates. |
diff --git a/src/frontend/src/content/docs/get-started/aspire-sdk.mdx b/src/frontend/src/content/docs/get-started/aspire-sdk.mdx
index 6016fdcff9..401adaf846 100644
--- a/src/frontend/src/content/docs/get-started/aspire-sdk.mdx
+++ b/src/frontend/src/content/docs/get-started/aspire-sdk.mdx
@@ -105,7 +105,7 @@ The Aspire SDK can source the binaries for these dependencies from platform-spec
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/).
When `AspireUseCliBundle` is `true`:
From 2f35c32b3903ca3a5eb637dc1d59cdae03bd7a23 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?S=C3=A9bastien=20Ros?=
<1165805+sebastienros@users.noreply.github.com>
Date: Fri, 13 Nov 2026 14:42:51 -0800
Subject: [PATCH 2/3] Fix CLI bundle defaults, ASPIRE010 trigger, and add
ASPIRE013 to sidebar
- 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)
---
src/frontend/config/sidebar/reference.topics.ts | 1 +
.../src/content/docs/diagnostics/aspire010.mdx | 8 ++++----
.../src/content/docs/get-started/aspire-sdk.mdx | 12 +++---------
3 files changed, 8 insertions(+), 13 deletions(-)
diff --git a/src/frontend/config/sidebar/reference.topics.ts b/src/frontend/config/sidebar/reference.topics.ts
index e93e30c950..1cdc6a12c1 100644
--- a/src/frontend/config/sidebar/reference.topics.ts
+++ b/src/frontend/config/sidebar/reference.topics.ts
@@ -808,6 +808,7 @@ export const referenceTopics: StarlightSidebarTopicsUserConfig[number] = {
{ label: 'ASPIRE008', link: '/diagnostics/aspire008' },
{ label: 'ASPIRE009', link: '/diagnostics/aspire009' },
{ label: 'ASPIRE011', link: '/diagnostics/aspire011' },
+ { label: 'ASPIRE013', link: '/diagnostics/aspire013' },
{
label: 'ASPIREACADOMAIN001',
link: '/diagnostics/aspireacadomains001',
diff --git a/src/frontend/src/content/docs/diagnostics/aspire010.mdx b/src/frontend/src/content/docs/diagnostics/aspire010.mdx
index 5dd9ac3811..de7f2e502c 100644
--- a/src/frontend/src/content/docs/diagnostics/aspire010.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspire010.mdx
@@ -15,7 +15,7 @@ import { Badge } from '@astrojs/starlight/components';
> '[ProjectName]' is configured with AspireUseCliBundle=false. Some Aspire features require the Aspire CLI bundle. Set AspireUseCliBundle=true to enable those features, or suppress ASPIRE010 to continue without the bundle. See https://aka.ms/aspire/diagnostics/aspire010 for more information.
-This diagnostic warning is reported when a non-C# AppHost project has `AspireUseCliBundle` explicitly set to `false`. Features that depend on the CLI bundle — such as resolving DCP and the Aspire Dashboard from the installed Aspire CLI instead of NuGet packages — remain unavailable.
+This diagnostic warning is reported when a non-C# AppHost project, such as an F# (`.fsproj`) or Visual Basic (`.vbproj`) project, has `AspireUseCliBundle` set to `false`. Because `false` is the default for these projects, the warning is also reported when the property isn't set. Features that depend on the CLI bundle — such as resolving DCP and the Aspire Dashboard from the installed Aspire CLI instead of NuGet packages — remain unavailable.
C# AppHosts require the CLI bundle and report error [`ASPIRE013`](/diagnostics/aspire013/) instead. The two diagnostics are mutually exclusive.
@@ -23,7 +23,7 @@ C# AppHosts require the CLI bundle and report error [`ASPIRE013`](/diagnostics/a
The following configuration in a non-C# AppHost produces `ASPIRE010`:
-```xml title="MyApp.AppHost.proj"
+```xml title="MyApp.AppHost.fsproj"
false
@@ -33,7 +33,7 @@ The following configuration in a non-C# AppHost produces `ASPIRE010`:
Set `AspireUseCliBundle` to `true` to opt in to CLI bundle delegation:
-```xml title="MyApp.AppHost.proj"
+```xml title="MyApp.AppHost.fsproj"
true
@@ -45,7 +45,7 @@ An unresolved bundle layout reports [`ASPIRE009`](/diagnostics/aspire009/). [`AS
If you intend to keep using NuGet-restored orchestration dependencies, suppress `ASPIRE010`:
-```xml title="MyApp.AppHost.proj"
+```xml title="MyApp.AppHost.fsproj"
false
$(NoWarn);ASPIRE010
diff --git a/src/frontend/src/content/docs/get-started/aspire-sdk.mdx b/src/frontend/src/content/docs/get-started/aspire-sdk.mdx
index 401adaf846..9ecaa3d265 100644
--- a/src/frontend/src/content/docs/get-started/aspire-sdk.mdx
+++ b/src/frontend/src/content/docs/get-started/aspire-sdk.mdx
@@ -105,7 +105,7 @@ The Aspire SDK can source the binaries for these dependencies from platform-spec
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. 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 (`.csproj` projects and single-file `apphost.cs` AppHosts) require the Aspire CLI bundle. `AspireUseCliBundle` defaults to `true` for them, so you don't need to set it. Setting it to any other value reports error [`ASPIRE013`](/diagnostics/aspire013/), and suppressing `ASPIRE013` doesn't bypass the requirement. Non-C# AppHosts, such as F# or Visual Basic projects, default to `false` and restore orchestration dependencies from NuGet packages. They report the suppressible warning [`ASPIRE010`](/diagnostics/aspire010/) until you set `AspireUseCliBundle` to `true`.
When `AspireUseCliBundle` is `true`:
@@ -122,20 +122,14 @@ When `AspireUseCliBundle` is `true`:
#### Enable the CLI bundle
-Set `AspireUseCliBundle` in your AppHost `.csproj`:
+C# AppHosts use the CLI bundle by default. To opt a non-C# AppHost, such as an F# project, in to the bundle, set `AspireUseCliBundle` in its project file:
-```xml title="MyApp.AppHost.csproj"
+```xml title="MyApp.AppHost.fsproj"
true
```
-For an existing single-file AppHost, set the equivalent `#:property` directive:
-
-```csharp title="apphost.cs"
-#:property AspireUseCliBundle=true
-```
-
:::note[Advanced scenario: Override the bundle path]
Most apps don't need to set either path. `AspireCliPath` selects an explicit `aspire` executable for invocation and bundle discovery. `AspireCliBundlePath` supplies an explicit unpacked bundle layout for DCP and Dashboard resolution, but it doesn't select the executable used to launch the AppHost:
From 1db920e6dae1c8871ac1770de8810a6bd105e5bf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?S=C3=A9bastien=20Ros?=
<1165805+sebastienros@users.noreply.github.com>
Date: Fri, 13 Nov 2026 15:27:14 -0800
Subject: [PATCH 3/3] Fix aspire destroy unknown-option sample failing CLI
options test
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.
---
src/frontend/.starlight-icons/safelist.json | 3 +++
.../content/docs/reference/cli/commands/aspire-destroy.mdx | 6 +-----
2 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/src/frontend/.starlight-icons/safelist.json b/src/frontend/.starlight-icons/safelist.json
index 8b9037434c..20f8fa07f8 100644
--- a/src/frontend/.starlight-icons/safelist.json
+++ b/src/frontend/.starlight-icons/safelist.json
@@ -40,8 +40,11 @@
"i-material-icon-theme:folder-src-open",
"i-material-icon-theme:folder-template",
"i-material-icon-theme:folder-template-open",
+ "i-material-icon-theme:folder-vscode",
+ "i-material-icon-theme:folder-vscode-open",
"i-material-icon-theme:git",
"i-material-icon-theme:go",
+ "i-material-icon-theme:go-mod",
"i-material-icon-theme:gradle",
"i-material-icon-theme:html",
"i-material-icon-theme:http",
diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-destroy.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-destroy.mdx
index 9b11c6b323..0b50b6a6e7 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-destroy.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-destroy.mdx
@@ -53,11 +53,7 @@ The destroy command requires --yes when the --non-interactive option is specifie
### Unknown arguments
-`aspire destroy` rejects unrecognized options and positional arguments before it discovers or starts the AppHost, so a mistyped option can't silently run the destroy pipeline. The command exits with code `1`:
-
-```bash title="Aspire CLI"
-aspire destroy --force
-```
+`aspire destroy` rejects unrecognized options and positional arguments before it discovers or starts the AppHost, so a mistyped option can't silently run the destroy pipeline. For example, passing `--force`, which isn't an `aspire destroy` option, exits with code `1` and reports:
```text title="Output"
Unrecognized command or argument '--force'.