Your whole distributed app, one F5 away.

The official Aspire extension for Visual Studio Code brings your AppHost, resources, debuggers, and dashboard into one development loop.
Get started ·
Documentation ·
Integrations
Start here
An AppHost defines your app in code: services, containers, databases, front ends, and the connections between them.
- Open an Aspire project or create a new one using the Aspire view.
- Choose your AppHost and press F5. Aspire starts every resource in the right order and connects supported debuggers.
- Use the Aspire view and Aspire Dashboard to follow resources, endpoints, logs, traces, and metrics.
A better inner dev loop
- Run your apps: Start, debug, and stop an Aspire application, or use the available start, stop, and restart actions for individual resources, from the Aspire view.
- Debug across your stack: Aspire debug sessions support C#, JavaScript, Python, Go, Java, and Rust application resources when the corresponding debugger is available. Java and Rust debugging require Aspire 13.6 or later. Go AppHosts (
apphost.go) are debugged with the Go extension's Delve adapter when the Go extension is installed.
- Attach to running resources: Attach to .NET and Go resources from the Aspire view. If a debugger extension is missing or disabled, open Extensions from the notification, install or enable it, and retry without restarting the AppHost.
- See live health and analytics: Open the Aspire dashboard for resource health, endpoints, console logs, structured logs, distributed traces, and metrics.
- Monitor without leaving VS Code: See resource health summaries and quick actions beside resource definitions in your AppHost.
- Move toward production. Deploy, publish artifacts, and run pipeline steps using the Aspire view.
AppHost launch profiles
Select a profile from your .NET AppHost's Properties/launchSettings.json (or apphost.run.json for a file-based AppHost) in .vscode/launch.json. This example selects h2; adjust program and the profile name for your AppHost:
{
"version": "0.2.0",
"configurations": [
{
"type": "aspire",
"request": "launch",
"name": "Nested h2",
"program": "${workspaceFolder}/AppHost/AppHost.csproj",
"dashboardBrowser": "none",
"debuggers": {
"apphost": {
"launchProfile": "h2"
}
}
}
]
}
For .NET AppHosts, debuggers.apphost.launchProfile takes precedence over debuggers.project.launchProfile, which takes precedence over top-level launchProfile.
The selection works with or without the C# extension, including Run Without Debugging. When the C# extension is disabled or not installed, the CLI must support --launch-profile; unsupported versions report an error instead of ignoring the selection. In this mode, launch profiles require the run command; publish, deploy, and do reject the selection.
Without the C# extension, disableLaunchProfile: true has no effect and displays a warning: the CLI still applies the default AppHost launch profile. Install or enable the C# extension to disable launch profiles.
Bring your stack
Aspire can bring together C#, TypeScript and JavaScript, Python, Go, Java, containers, databases, cloud resources, and more. Browse the integration gallery to find the pieces your app needs.
Go AppHost debugging (Preview)
Go AppHosts support resource CodeLens and gutter state indicators. Debugging an apphost.go requires the Go extension and Delve. If Go debugger support is missing or disabled, Debug offers setup instead of starting the AppHost without a debugger; Run Without Debugging remains available. The same setup check applies to Java and Rust AppHosts.
The Go extension selects the debugger's Go toolchain through its own settings (go.goroot and go.alternateTools), while Aspire CLI resolves go on its environment's PATH. Keep those selections aligned when using multiple Go installations. Aspire does not override the Go extension's toolchain settings.
The extension contributes aspire_apphost_start, aspire_apphost_stop, and aspire_resource_debug language model tools. They only accept AppHosts and resources already discovered in a trusted workspace, reject arbitrary or absolute paths, and ask the user to confirm before acting. Resource debugging attaches to a running resource, including .NET and Go resources started with Run Without Debugging in VS Code; it does not start or restart one.
Go resources started with Run Without Debugging use DCP-managed go run, just like CLI starts, so the debugger can attach later. Actual debug launches still use VS Code and Delve; debuggers.go overrides apply to those IDE-managed launches.
Attachment to a .NET resource launched by dotnet watch is unavailable when arguments follow its first --. SDK versions interpret that separator differently, so Aspire declines attachment rather than guessing which build output is running. The resource continues running; normal dotnet run launches are unaffected.
Resource-debug confirmation is bound to the resolved AppHost. If discovery initially fails or a path points to a different AppHost before attachment, the tool refuses the operation; retry with a fresh confirmation after the intended AppHost has been discovered.
Learn more
Feedback and contributions
Found a bug or have an idea? Report an issue or request a feature.
Interested in contributing to the Aspire VS Code experience? Read the contributor guide and pick up a good first issue.
License
See LICENSE.TXT for details.