[NETSDKE2E][Green] After debugging the blazorwasm project, it will automatically stop.

[yinjiehe01]

REGRESSION INFO
This issue does not repro on April Prerelease 1 C#DK 3.11.200(with C# 2.134.7).

INSTALL STEPS

OS: Linux

1. Install the SDK 10.0.202
2. Install VS Code Stable - 1.116.0
3. Install April prerelease 3 C# 2.135.19
4. Install April prerelease 3 C# DK 3.13.205

REPRO STEPS

1. Open VS Code > Create .NET Project > Blazor WebAssembly Standalone App
2. F1-> Debug:Select and Start Debugging ->C# -> C#:webapp [Default Configuration]

ACTUAL
The Blazorwasm project will automatically exit debugging.

EXPECTED
The project will remain in debug mode

[LittleLittleCloud]

@yinjiehe01 can you upgrade C# extension to 2.135.19 and give another shot? The C# 2.134.7 has a known issue in version mismatch on debug && hotreload related brokerage service and should be addressed in latest C# prerelease

In the meantime, can you also share your dotnet --info, wondering which SDK are you using.

[vsccarl]

@LittleLittleCloud I can repro with C# 2.135.19

dotnet --info

Host:
  Version:      10.0.7
  Architecture: x64
  Commit:       b16286c228
  RID:          linux-x64

.NET SDKs installed:
  10.0.203 [/usr/lib/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 10.0.7 [/usr/lib/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 10.0.7 [/usr/lib/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
  None

Environment variables:
  DOTNET_BUNDLE_EXTRACT_BASE_DIR           [/home/vsccarl/.cache/dotnet_bundle_extract]

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download

[LittleLittleCloud]

@vsccarl Thanks for the quick reply,

when the blazorwasm project stop, did you also see mono warning prompt in vscode like what mentioned in issue #3002

[yinjiehe01]

@LittleLittleCloud we found if debugging the blazorwasm project by ctrl + F5 or start with debugging, it can run successfully and then run the same project with Start New Instance or command Debug:Select and Start Debugging , it will show the same warning prompt mentioned in issue #3002

[LittleLittleCloud]

Thanks for confirming, I think it's a dup of #3002 , let's close this issue and tracking the bug there