Add a walkthrough to install aspire CLI#12574
Closed
adamint wants to merge 6 commits intomicrosoft:mainfrom
Closed
Add a walkthrough to install aspire CLI#12574adamint wants to merge 6 commits intomicrosoft:mainfrom
adamint wants to merge 6 commits intomicrosoft:mainfrom
Conversation
Contributor
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 12574Or
iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 12574" |
adamint
commented
Oct 31, 2025
|
|
||
|
|
||
| getAspireCliExecutablePath(surroundWithQuotes: boolean = true): string { | ||
| getAspireCliExecutablePath(): string { |
Member
Author
There was a problem hiding this comment.
Simplifies getting the path and moves quoting/adding an ampersand on windows to sendAspireCommandToAspireTerminal
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds a VS Code walkthrough experience for new Aspire users, guiding them through CLI installation, verification, and getting started with Aspire projects. It also refactors the CLI path handling to properly support paths with special characters across different platforms.
Key changes:
- Added a multi-step walkthrough with install, restart, verify, and next steps guidance
- Refactored CLI path quoting logic to handle Windows PowerShell and Unix shells differently
- Added CLI availability checks before command execution and debug sessions
- Created comprehensive tests for CLI path handling
Reviewed Changes
Copilot reviewed 16 out of 16 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| extension/walkthrough/*.md | Four markdown files providing walkthrough step content for CLI installation, VS Code restart, verification, and next steps |
| extension/src/walkthroughCommands.ts | New file implementing CLI verification, installation commands, and availability checks |
| extension/src/utils/AspireTerminalProvider.ts | Refactored path quoting to use platform-specific shell syntax (PowerShell & on Windows, proper escaping on Unix) |
| extension/src/utils/workspace.ts | Updated to use simplified CLI path method without quoting parameter |
| extension/src/test/aspireTerminalProvider.test.ts | Comprehensive tests for CLI path retrieval with various edge cases |
| extension/src/loc/strings.ts | Added localized strings for walkthrough messages |
| extension/src/extension.ts | Registered new walkthrough commands and added CLI availability checks |
| extension/src/debugger/AspireDebugSession.ts | Updated to use simplified CLI path method |
| extension/src/debugger/AspireDebugConfigurationProvider.ts | Added CLI availability check before starting debug sessions |
| extension/package.nls.json | Added localization entries for walkthrough strings |
| extension/package.json | Defined walkthrough contribution with steps and completion events |
| extension/loc/xlf/aspire-vscode.xlf | Added translation units for new localized strings |
| .github/copilot-instructions.md | Added TypeScript and localization guidelines for extension development |
Member
Author
|
hold for post-release |
16 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Solves the problems of
When running an aspire vs code command or starting a new debug session, this adds a check that aspire is actually available on the path to use. If it is, the command is sent to the terminal/debug session can start (I've updated the logic around what specifically gets sent in
AspireTerminalProviderto work in pwsh).If aspire is not on the path, we show this error, which will navigate you directly to the CLI installation instructions in the readme. Unfortunately, programmatically opening the walkthrough I created does not consistently work, hence this alternative.

When first installing the Aspire extension, you will see a walkthrough - see screenshots for each step below (install, restart VS code, verify, next steps). I decided on asking the user to restart VS Code because a reload will not refresh the environment (PATH is not updated).
Walkthrough steps
Feel free to change the markdown text for any of them. Most is copilot-generated
Install CLI
Runs the same commands as in our readme.
Restart VS Code
Verify installation
(users see this on failure)

Next steps
Fixes #11910
Checklist
<remarks />and<code />elements on your triple slash comments?doc-ideatemplatebreaking-changetemplatediagnostictemplate