Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ The workspace must be trusted, and the VS Code host must support the language mo

When an AppHost is running, the extension paints live state directly into your editor.

**CodeLens** appears above each resource definition in C# and TypeScript AppHosts. It shows the current state and health and exposes one-click `Start`, `Stop`, `Restart`, and `View Logs` actions in addition to any custom commands the resource publishes.
**CodeLens** appears above each resource definition in C#, TypeScript, and Go AppHosts. It shows the current state and health and exposes one-click `Start`, `Stop`, `Restart`, and `View Logs` actions in addition to any custom commands the resource publishes.

**Editor title bar buttons** add **Run Aspire AppHost** and **Debug Aspire AppHost** actions next to the standard Run/Debug buttons whenever you have an AppHost file open.

Expand Down Expand Up @@ -272,6 +272,8 @@ The extension detects each resource's language and attaches the right debugger:

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.

When you debug a Go, Java, or Rust AppHost and the required debugger extension isn't installed, the Aspire extension offers its debugger setup flow first. Selecting **Set Up** or dismissing the prompt cancels that launch without showing a duplicate launch-failure notification. **Run Without Debugging** remains available. For Go, the `golang.go` extension's toolchain settings govern the debugger, while the Aspire CLI resolves Go from its environment.

## Feedback and issues

Found a bug or have an idea? File it on the [microsoft/aspire](https://github.com/microsoft/aspire/issues) repo:
Expand Down
Loading