[WebToolsE2E] When running an Aspire Starter App in VS Code using "Debug > Start New Instance", apiservice remains unhealthy and webfrontend stays waiting

[cyimperial]

REGRESSION INFO: Works well in May pre-release 7 C# DevKit Prerelease Version 3.27.196; C# Ext Prerelease 2.146.2

INSTALL STEPS

1. OS: Windows x64
2. Install the SDK 10.0.302
3. Install VS Code insiders - v1.130
4. Install latest candidate build from C#: [Pipelines - Run 2.147.47] and C# Dev Kit: [Pipelines - Run 3.27.199]
5. Aspire CLI

REPRO STEPS

1. Create .NET Project > Aspire Starter App > name it AspireApp1.
2. Under Solution Explorer, right-click AspireApp1.AppHost.
3. Select Debug > Start New Instance.
4. Wait for the Aspire Dashboard to load.

Note:

• Repro with F5
• Repro with Aspire 13.4.6

The issue is not reproducible when running the project from the command line:

cd AspireApp1.AppHost
dotnet run

The Aspire application starts successfully, all resources become healthy, and the application functions as expected.

ACTUAL Launching the Aspire Starter App through Debug > Start New Instance causes apiservice to remain in a Running (Unhealthy) state and webfrontend to remain in a Waiting state indefinitely."

EXPECTED Launching the Aspire Starter App through Debug > Start New Instance should start all resources successfully, with apiservice becoming healthy and webfrontend transitioning to a Running state.

[claudiaregio]

@vsccarl Could you or original poster validate if this reproduces on latest main?

[vsccarl]

@claudiaregio fixed in latest main. Still reproduces in prerelease, including 3.27.199.

[claudiaregio]

@vsccarl ok thank you! going to close then since next snap will get rid of this