From 77043fe1909f5acca0932519bf65c07bae077715 Mon Sep 17 00:00:00 2001 From: "aspire-repo-bot[bot]" <268009190+aspire-repo-bot[bot]@users.noreply.github.com> Date: Thu, 3 Sep 2026 18:26:10 +0000 Subject: [PATCH] Document Aspire CLI debug log location in VS Code extension docs Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../src/content/docs/get-started/aspire-vscode-extension.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx index 41d941a41..cf9450974 100644 --- a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx +++ b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx @@ -107,6 +107,10 @@ The Aspire Dashboard is no longer opened by default when the AppHost starts, as If the AppHost fails to build during a run or debug launch, VS Code shows a single error notification with **Open CLI Log** and, when available, **Open AppHost Log** actions that open the relevant log file directly in a non-preview editor. Full diagnostics and log locations are still available in the Debug Console. ::: +:::note[CLI debug logging] +Enable the **Aspire: Enable Aspire Cli Debug Logging** setting (`aspire.enableCliDebugLogging`) to get console debug output for Aspire CLI commands executed by the extension. Persisted CLI log files are always written to the [Aspire home directory's `logs` folder](/get-started/troubleshooting/#cli-logs) (`~/.aspire/logs` by default), regardless of this setting. +::: + **Aspire: Configure launch.json file** adds a minimal launch configuration `.vscode/launch.json` that supports AppHosts written in any language. AppHosts are discovered automatically in the workspace.