| name | aspire-cli-install |
| description | Migrating .NET Aspire repos from workload install to CLI script install |
| domain | aspire, dotnet, devops |
| confidence | high |
| source | earned (verified against https://aspire.dev/get-started/install-cli/ on 2026-04-20; package upgrade to 13.2.2 validated) |
Context
The .NET Aspire team deprecated the dotnet workload install aspire command and replaced it with a standalone CLI installed via install scripts. This affects all .NET Aspire repositories that document installation steps or configure devcontainers.
Patterns
Installation Commands
Bash (Linux/macOS):
curl -sSL https://aspire.dev/install.sh | bash
PowerShell (Windows):
iex "& { $(irm https://aspire.dev/install.ps1) }"
Validation:
aspire --version
Where to Look in a Repo
- README / main docs — Check for references to "Aspire workload" or
dotnet workload install aspire
- Deployment / architecture docs — Often contain prerequisite sections with install steps
- Session / workshop docs —
Prerequisites.md, Installation.md, etc.
- Devcontainer config —
.devcontainer/devcontainer.json postCreateCommand or onCreateCommand
- CI/CD pipelines — GitHub Actions, Azure Pipelines may have setup steps
Migration Checklist
Examples
Documentation Update (Markdown)
Before:
2. **.NET Aspire Workload**
```bash
dotnet workload install aspire
**After:**
```markdown
2. **Aspire CLI**
The Aspire CLI is installed via an install script (the old `dotnet workload install aspire` is obsolete).
**Bash (Linux/macOS):**
```bash
curl -sSL https://aspire.dev/install.sh | bash
PowerShell (Windows):
iex "& { $(irm https://aspire.dev/install.ps1) }"
Verify installation:
aspire --version
See https://aspire.dev/get-started/install-cli/ for details.
### Devcontainer Update
**Before:**
```json
"postCreateCommand": "dotnet workload install aspire"
After:
"postCreateCommand": "curl -sSL https://aspire.dev/install.sh | bash"
Anti-Patterns
- ❌ Leaving
dotnet workload install aspire in docs or devcontainer — it's obsolete
- ❌ Only showing one OS variant (bash or PowerShell) in cross-platform docs — show both
- ❌ Not including
aspire --version validation step — developers need to confirm the install worked
- ❌ Not linking to https://aspire.dev/get-started/install-cli/ — official source is authoritative
- ❌ Using "Aspire workload" terminology in new docs — the workload concept is deprecated for Aspire