Repository navigation
[VS Code] Add "Go to source" action for source-backed resources #20424
Copy link
Copy link
Open
Labels
area-vscodetriage:bot-seenAspire triage bot has seen this issueAspire triage bot has seen this issue
Milestone
Description
Activity
added on Sep 24, 2026
area-app-modelIssues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplicationIssues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication
added and removed on Sep 24, 2026
area-app-modelIssues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplicationIssues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication
🤖 Aspire triage pass — 2026-09-24 07:02 UTC
Area: area-vscode-extension
Kind: feature-request
Repro: none — the issue describes a proposed navigation experience rather than a failing scenario
Affected version(s): not version-specific (latest: 13.5.4)
Severity: S4 — UX enhancement; no existing core scenario is reported broken
Urgency: ⚪ backlog — no milestone
Reason: concrete feature request, but not important or actionable enough for 13.6
Suggested owner(s): Adam Ratzman (@adamint) (score 398), backup Ella Hathaway (@ellahathaway) (score 148)
Evidence:
- adamint merged Complete managed Blazor WebAssembly debugging in VS Code #20001, Fix Rust AppHost run-session notification routing #19831, Fix VS Code debugger guidance E2E contract #19702, Prevent repeated Hot Reload advisory #19672, Rewrite the Aspire extension README and walkthrough #19632 in
area-vscode-extension(last 90d) - adamint closed STOP bugging me to enable hot-reload #19544, [VS Code] Open CLI diagnostic logs automatically after command failures #19511, Tracking: open VS Code extension issues with no active PR #19066, VS Code Extension fails to start File Based app host, when
aspire runworks #18911, [Failing test]: VS Code extension E2E 'global debug stop removes running apphost' times out waiting for AppHost to stop #18524 as completed inarea-vscode-extension - ellahathaway merged Fix Azure Functions E2E HTTPS endpoint readiness race #20067, Stabilize Deno debugger breakpoint setup #20020, Fix unpackaged WinUI debugging in VS Code #19877, Keep Aspire CLI notification claim timestamps consistent #19854, Prevent Aspire view from stealing sidebar focus #19754 in
area-vscode-extension(last 90d)
Confidence: high
Needs human?: no
added on Sep 24, 2026
triage:bot-seenAspire triage bot has seen this issueAspire triage bot has seen this issue
Metadata
Metadata
Assignees
Labels
area-vscodetriage:bot-seenAspire triage bot has seen this issueAspire triage bot has seen this issue
Summary
Source-backed Aspire resources, such as a .NET project, should expose a Go to source action in the VS Code extension.
Selecting the action would switch focus to the VS Code Explorer and reveal/select the resource's source location. For a .NET project resource, this could select the project file or project directory.
Motivation
The Aspire resource view is useful for understanding and operating a distributed application, but moving from a running resource back to its implementation currently requires manually finding the corresponding project in the workspace.
This becomes increasingly cumbersome in larger solutions, multi-root workspaces, and applications containing similarly named projects. The resource already has source metadata, so the extension can provide a direct navigation path.
Proposed experience
Add Go to source to the context menu or actions for resources that have a local source location.
When invoked, the extension should:
For example:
.csprojor its containing directory.Expected behavior
Possible placement
The context-menu option would provide the most direct equivalent to existing VS Code navigation actions such as revealing a file in the Explorer.