Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/frontend/src/content/docs/get-started/aspire-sdk.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -162,6 +162,8 @@ When `AspireUseCliBundle` is `true` and you start the AppHost with `dotnet run`
- **`Dnx`** — always invokes the Aspire CLI through `dnx`, using the unversioned `Aspire.Cli` package. This honors an in-scope [.NET local tool manifest](https://learn.microsoft.com/dotnet/core/tools/local-tools-how-to-use#create-a-manifest-file) (`.config/dotnet-tools.json`) if one pins `Aspire.Cli`, or resolves the latest published package when no manifest applies.
- **`DnxPinned`** — always invokes the Aspire CLI through `dnx`, using `Aspire.Cli@<version>` pinned to the exact `Aspire.Cli` version paired with `Aspire.AppHost.Sdk`. Use this when the CLI must match the AppHost SDK version exactly, ignoring any local tool manifest.

The pinned mode also uses a version-specific bundle. Unless you set `AspireCliPath` or `AspireCliBundlePath`, the SDK resolves the bundle only from `$ASPIRE_HOME/dnx/aspire.cli/<version>` (by default under `~/.aspire`). It runs `aspire setup` into that directory when it doesn't exist yet, so a bundle left by a different global Aspire CLI version is never used and the global CLI's bundle layout isn't modified.

Set `AspireCliInvocationMode` in your AppHost `.csproj`:

```xml title="MyApp.AppHost.csproj"
Expand Down
Loading