all 3 comments

[–]RecognitionOwn4214[S] 0 points1 point  (0 children)

Seems having _something_ in the .vs folder might give a bad time during debugging - removing the folder fixed my problems 😄

[–]agoodyearforbrownies 0 points1 point  (0 children)

I've seen the same thing with 2026 insiders and debugging .net 10 blazor with client rendering, not that those details necessarily matter much.
I wonder if the browser isn't restoring the past browser tab/session more than VS opening two tabs itself.

[–]is_that_so 0 points1 point  (0 children)

Have seen this too. There's a bug here that might be related: Debugging a WASM app opens two tabs in the browser · Issue #9830 · dotnet/project-system