Skip to content
Merged
Show file tree
Hide file tree
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 @@ -178,6 +178,8 @@ Use an IDE workflow when you want the IDE to manage debugging or hot reload for

Use the Aspire extension for Visual Studio Code when you want VS Code to start the AppHost, attach debuggers, and manage supported resource debugging experiences. VS Code hot reload or framework-specific refresh behavior still belongs to the debugger or framework backing the resource, not to Aspire restart, rebuild, or watch behavior.

Coding agents can call the extension's `aspire_hot_reload_status` language model tool to check whether C# Dev Kit Hot Reload can reach a resource. Having Hot Reload enabled doesn't mean that it applies to every resource. It applies only to .NET project resources that this VS Code window launched under the debugger. Resources started with **Run Without Debugging**, and resources in AppHosts that run outside the window, such as with `aspire start`, don't qualify. If an edit doesn't take effect, restart the resource first. If that doesn't help, rebuild and restart the AppHost. For the tool's inputs and outcomes, see the [language model tool reference](/get-started/aspire-vscode-extension/#language-model-tool-reference).

### Visual Studio

Use Visual Studio when you want its built-in debugging and hot reload experience for supported resources. Visual Studio can run and debug Aspire apps, but IDE hot reload is still separate from Aspire restart, rebuild, and watch behavior.
Expand Down
Loading
Loading