✨ Feature Request: Support Installing Aspire CLI via `winget`

[asilverman]

Summary

Please add official support for installing the Aspire CLI using Windows Package Manager (winget) as an alternative to the current PowerShell and dotnet installation methods.

Today, Windows users can only install Aspire via:

• PowerShell script
• dotnet tool install

However, winget is now a first-class, native package manager on Windows and is widely used in enterprise and developer environments.

Current Installation Methods

From the documentation:
https://aspire.dev/get-started/install-cli/

• ✅ PowerShell script
• ✅ dotnet tool install
• ❌ winget not supported

Requested Enhancement

Add an official winget package so users can install Aspire with:

winget install Aspire.AspireCli

(or similar official package ID)

Why This Matters

• ✅ Aligns Aspire with modern Windows package management
• ✅ Improves enterprise adoption (winget is standard in managed environments)
• ✅ Enables easier automation via Intune, Dev Box, CI images, and provisioning scripts
• ✅ Consistent with how many other developer tools are installed (Git, Node, Docker, Azure CLI, etc.)
• ✅ Reduces friction for onboarding new developers

Expected Behavior

• Aspire CLI is officially published and maintained in the WinGet Community Repository

• Supports:

  • winget install
  • winget upgrade
  • winget uninstall

• Version parity with current PowerShell and dotnet releases

Additional Context

Many Windows developers now standardize all tooling via winget. Not supporting it creates an unnecessary gap in Aspire’s otherwise excellent developer experience.