[docs] Document Aspire CLI debug log location in VS Code extension - #1613
Draft
aspire-repo-bot[bot] wants to merge 1 commit into
Draft
[docs] Document Aspire CLI debug log location in VS Code extension#1613aspire-repo-bot[bot] wants to merge 1 commit into
aspire-repo-bot[bot] wants to merge 1 commit into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aspire-repo-bot
Bot
added
the
docs-from-code
14 tasks
Contributor
Author
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Documents changes from microsoft/aspire#19868
@ellahathawayTargeting
release/13.6based on the source PR milestone13.6.Why
Source PR #19868 clarified the description of the Enable Aspire Cli Debug Logging VS Code setting so it also tells users where persisted CLI log files are written: the Aspire home directory's
logsfolder (~/.aspire/logsby default). The Aspire docs did not previously connect this setting to the log location, even thoughget-started/troubleshooting.mdxalready documents CLI log locations generally.What changed
src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx: added a new:::note[CLI debug logging]admonition (next to the existing "Build failure notifications" note in the "Run, debug, and deploy" section) explaining theaspire.enableCliDebugLoggingsetting and cross-linking to the existingtroubleshooting.mdx#cli-logssection for the log file location.No new pages were created; this is a targeted addition to an existing page.