From 8817287f39e85956a42fc6942c6caedf73b73c37 Mon Sep 17 00:00:00 2001 From: "aspire-repo-bot[bot]" <268009190+aspire-repo-bot[bot]@users.noreply.github.com> Date: Fri, 30 Oct 2026 02:32:30 +0000 Subject: [PATCH 1/3] Document Go AppHost debugging in VS Code extension Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../src/content/docs/get-started/aspire-vscode-extension.mdx | 3 +++ 1 file changed, 3 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 5381d1438d..4a8b382c44 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 @@ -266,10 +266,13 @@ The extension detects each resource's language and attaches the right debugger: | Node.js / Browser apps | `js-debug` | None (built into VS Code) | | Python | `debugpy` | [Python](https://marketplace.visualstudio.com/items?itemName=ms-python.python) | | Java | `java` | [Language Support for Java](https://marketplace.visualstudio.com/items?itemName=redhat.java) and [Debugger for Java](https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-debug) | +| Go | `go` (Delve) | [Go](https://marketplace.visualstudio.com/items?itemName=golang.go) | | C# / .NET | `coreclr` | [C# Dev Kit](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit) (recommended) or [C#](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csharp) | | Azure Functions, C# / .NET | `coreclr` | [Azure Functions](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurefunctions) plus [C#](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csharp) | | Azure Functions, JavaScript / TypeScript | `js-debug` | None (built into VS Code) | +Go AppHosts (`apphost.go`) can also be run and debugged from the Aspire view or . The extension runs the CLI's `go run ` command through the Go extension's Delve adapter, using the AppHost directory as the program and forwarding the AppHost's own arguments. If the command isn't `go run ` (for example, it includes `go run` flags such as `-tags`), or the Go extension isn't installed, the extension shows an error instead of debugging the wrong program. Toolbar restart of a Go AppHost session performs the ordered Aspire restart. + For TypeScript or JavaScript Azure Functions apps, the Aspire extension reserves a loopback Node inspector port until task launch, starts Azure Functions Core Tools as a task, and attaches VS Code's built-in `pwa-node` debugger. Stopping the Aspire debug session also stops the Functions task. The Azure Functions VS Code extension isn't required for these apps. ## Feedback and issues From b3f64298da7c24006d5f1a4df032db2fda789d51 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Ros?= <1165805+sebastienros@users.noreply.github.com> Date: Fri, 13 Nov 2026 14:45:04 -0800 Subject: [PATCH 2/3] Move Go AppHost debugging note to Run, debug, and deploy; drop internals --- .../content/docs/get-started/aspire-vscode-extension.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) 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 ada13da8aa..ae571bec6e 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 @@ -16,7 +16,7 @@ import { Kbd } from 'starlight-kbd/components'; import ApiReference from '@components/ApiReference.astro'; The official Aspire extension for [Visual Studio Code](https://code.visualstudio.com/) turns VS Code into a first-class environment for building, debugging, and shipping [polyglot](/get-started/glossary/#polyglot) Aspire apps. -Press to build your AppHost, start your resources, and debug supported resource types — including C#, TypeScript, Java, Python, browser apps, and Azure Functions — alongside the Aspire dashboard. +Press to build your AppHost, start your resources, and debug supported resource types — including C#, TypeScript, Java, Python, Go, browser apps, and Azure Functions — alongside the Aspire dashboard. :::note[Prerequisites] A recent version of [Visual Studio Code](https://code.visualstudio.com/) and the **Aspire CLI** — install the CLI via the **Aspire: Install Aspire CLI** command from the Command Palette, or follow the [installation guide](/get-started/install-cli/). @@ -180,6 +180,8 @@ Enable the **Aspire: Enable Aspire Cli Debug Logging** setting (`aspire.enableAs **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. +Go AppHosts (`apphost.go`) run and debug the same way, using the [Go extension](https://marketplace.visualstudio.com/items?itemName=golang.go)'s Delve debugger. If the Go extension isn't installed, the Aspire extension shows an error instead of starting the AppHost. + To launch a specific AppHost, configure an [aspire.config.json](/reference/cli/configuration/) with an `appHost.path` property. @@ -273,8 +275,6 @@ The extension detects each resource's language and attaches the right debugger: | Azure Functions, C# / .NET | `coreclr` | [Azure Functions](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurefunctions) plus [C#](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csharp) | | Azure Functions, JavaScript / TypeScript | `js-debug` | None (built into VS Code) | -Go AppHosts (`apphost.go`) can also be run and debugged from the Aspire view or . The extension runs the CLI's `go run ` command through the Go extension's Delve adapter, using the AppHost directory as the program and forwarding the AppHost's own arguments. If the command isn't `go run ` (for example, it includes `go run` flags such as `-tags`), or the Go extension isn't installed, the extension shows an error instead of debugging the wrong program. Toolbar restart of a Go AppHost session performs the ordered Aspire restart. - For TypeScript or JavaScript Azure Functions apps, the Aspire extension reserves a loopback Node inspector port until task launch, starts Azure Functions Core Tools as a task, and attaches VS Code's built-in `pwa-node` debugger. Stopping the Aspire debug session also stops the Functions task. The Azure Functions VS Code extension isn't required for these apps. ## Feedback and issues From 1db920e6dae1c8871ac1770de8810a6bd105e5bf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Ros?= <1165805+sebastienros@users.noreply.github.com> Date: Fri, 13 Nov 2026 15:27:14 -0800 Subject: [PATCH 3/3] Fix aspire destroy unknown-option sample failing CLI options test The unknown-arguments example ran 'aspire destroy --force' in a bash block, which the pipeline command options unit test flags as an undocumented option. Describe the invalid option in prose and keep the error output. --- src/frontend/.starlight-icons/safelist.json | 3 +++ .../content/docs/reference/cli/commands/aspire-destroy.mdx | 6 +----- 2 files changed, 4 insertions(+), 5 deletions(-) diff --git a/src/frontend/.starlight-icons/safelist.json b/src/frontend/.starlight-icons/safelist.json index 8b9037434c..20f8fa07f8 100644 --- a/src/frontend/.starlight-icons/safelist.json +++ b/src/frontend/.starlight-icons/safelist.json @@ -40,8 +40,11 @@ "i-material-icon-theme:folder-src-open", "i-material-icon-theme:folder-template", "i-material-icon-theme:folder-template-open", + "i-material-icon-theme:folder-vscode", + "i-material-icon-theme:folder-vscode-open", "i-material-icon-theme:git", "i-material-icon-theme:go", + "i-material-icon-theme:go-mod", "i-material-icon-theme:gradle", "i-material-icon-theme:html", "i-material-icon-theme:http", diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-destroy.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-destroy.mdx index 9b11c6b323..0b50b6a6e7 100644 --- a/src/frontend/src/content/docs/reference/cli/commands/aspire-destroy.mdx +++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-destroy.mdx @@ -53,11 +53,7 @@ The destroy command requires --yes when the --non-interactive option is specifie ### Unknown arguments -`aspire destroy` rejects unrecognized options and positional arguments before it discovers or starts the AppHost, so a mistyped option can't silently run the destroy pipeline. The command exits with code `1`: - -```bash title="Aspire CLI" -aspire destroy --force -``` +`aspire destroy` rejects unrecognized options and positional arguments before it discovers or starts the AppHost, so a mistyped option can't silently run the destroy pipeline. For example, passing `--force`, which isn't an `aspire destroy` option, exits with code `1` and reports: ```text title="Output" Unrecognized command or argument '--force'.