[area-blazor] When debugging the Blazor WebAssembly project, the breakpoint in Counter.razor file can't be hit

[EmilyFeng97]

Regression info: Works well with .NET11 Preview 5 and previous P6

Install Steps

1. Clean machine: Win11 x64 ENU 25H2
2. Install VS Code Stable 1.126.0
3. Install .Net 11.0 preview 6 SDK from https://release.dot.net/
4. Add feed

Repro Steps

1. Open a normal Command Prompt (do not run as administrator).
2. Create a Blazor Web App - WebAssembly project and open it with vs code

   dotnet new blazor -int WebAssembly -o BlazorWASM
   cd BlazorWASM
   code .
   

3. Open the BlazorWASM.Client/Pages/Counter.razor file, place a breakpoint at method @code{} (line 17)
4. Navigate to the explorer, right click the *.csproj file > debug > Start New Instance
5. After the project opens in the browser, click the "Click me" button in Counter page.

Note:

1. This issue also repro on Blazor WebAssembly Standalone project.
2. This does not repro with Blazor Web App - Server/Auto project
3. This does not repro on .NET 10/9 projects
4. This issue also repro when debugging with VS 18.9 Insider.

Actual:

[jinzhao1127]

@javiercn, please look at this issue.
cc: @balachir

[lewing]

@javiercn @maraf is this gateway/aspire related?

[javiercn]

It shouldn't be. @maraf can you take a look at this?

[lewing]

The old DevServer called  app.UseWebAssemblyDebugging(). The new Gateway doesn't? The templates do it directly in Program.cs I think?

[lewing]

#67548

[lewing]

The latest build (I just tested 11.0.100-preview.6.26351.102) shouldn't have this problem and should not require the pr. The template in the build you tested was still using inspectURI which would require the pr. Please retest, closing the pr for now.

[EmilyFeng97]

The latest build (I just tested 11.0.100-preview.6.26351.102) shouldn't have this problem and should not require the pr. The template in the build you tested was still using inspectURI which would require the pr. Please retest, closing the pr for now.

This issue still repro on the latest build 11.0.100-preview.6.26351.107 SDK from https://aka.ms/dotnet/11.0.1xx-preview6/daily/dotnet-sdk-win-x64.exe.

1. It still repro when the breakpoint is set at line17 (currentCount++;)
2. it does not repro when the breakpoint is set at line13 (private int currentCount = 0;)

[maraf]

@EmilyFeng97 Could you please check if the app launchSettings.json contains inspectUri field?

[EmilyFeng97]

@EmilyFeng97 Could you please check if the app launchSettings.json contains inspectUri field?

After installing the latest SDK (11.0.100-preview.6.26351.113), the launchSettings.json file of the Blazor WebAssembly project does not contain the inspectUri field.

If I manually add the "inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}", to launchSettings.json file, this issue does not reproduce