[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]

Scott Carlton (@vsccarl) Could you or original poster validate if this reproduces on latest main?

[vsccarl]

Claudia Regio (@claudiaregio) fixed in latest main. Still reproduces in prerelease, including 3.27.199.

[claudiaregio]

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

[v-korosales]

The issue was reproduced using SDK 10.0.400 + May Prerelease 10 C# 2.149.33, C# Dev Kit 3.29.214

[v-elenafeng]

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

Hi Claudia Regio (@claudiaregio), this issue still exists in the latest V1 prerelease (10), do you mean that this issue will only be fixed in V2 prerelease 1 (where it won't be reproduced) and there are no plans to fix it in the V1 stable release? Am I understanding correctly?

cc: Jake (@JakeRadMSFT) Scott Carlton (@vsccarl)

[LittleLittleCloud]

Workaround: disable hotreload

[v-korosales]

Not reproduced with SDK 10.0.401 + C# DK V3 Stable 3.40.202 + C# 2.151.28 (public prerelease) + Aspire 13.6

[v-elenafeng]

Status: fixed