Context
In microsoft/aspire#14599 (targeting 13.2), the aspire setup command was folded into aspire doctor. The doctor command now auto-extracts the embedded bundle when running from a bundled CLI binary, before performing environment checks.
The setup command is now hidden but still works for backward compatibility.
What needs updating
Any aspire.dev documentation that references:
aspire setup → should use aspire doctor insteadaspire setup --force → should use aspire doctor (doctor handles extraction automatically)
Other CLI changes in 13.2
For completeness, here are the other CLI option changes that may affect docs:
--debug-level/-v → --log-level/-l (old flags still work as hidden backward-compat)-v is now a short alias for --version (standard CLI convention)--watch on describe → --follow/-f--format option description standardized to 'Output format (Table or Json).' across all commands
Context
In microsoft/aspire#14599 (targeting 13.2), the
aspire setupcommand was folded intoaspire doctor. The doctor command now auto-extracts the embedded bundle when running from a bundled CLI binary, before performing environment checks.The
setupcommand is now hidden but still works for backward compatibility.What needs updating
Any aspire.dev documentation that references:
aspire setup→ should useaspire doctorinsteadaspire setup --force→ should useaspire doctor(doctor handles extraction automatically)Other CLI changes in 13.2
For completeness, here are the other CLI option changes that may affect docs:
--debug-level/-v→--log-level/-l(old flags still work as hidden backward-compat)-vis now a short alias for--version(standard CLI convention)--watchon describe →--follow/-f--formatoption description standardized to 'Output format (Table or Json).' across all commands