razor icon indicating copy to clipboard operation
razor copied to clipboard

Cannot debug

Open uecasm opened this issue 3 years ago • 6 comments

Describe the bug: Pressing F5 to start debugging opens a new Chrome window to about:blank, and displays some DLL loading messages in the debug console. Nothing else happens. Clicking Stop Debugging does nothing; it does not appear to be possible to terminate the debugging session in any way other than using Close Window.

Version used:

  • .NET SDK (6.0.200)
  • Visual Studio Code 1.64.2 (also happens in 1.65.0)
  • C# 1.24.1
  • Microsoft.AspNetCore.Razor.VSCode.BlazorWasmDebuggingExtension 1.1.0

To reproduce: Steps to reproduce the behavior:

  1. Create a new Blazor WebAssembly app using the dotnet command line dotnet new blazorwasm -o BlazorApp --no-https
  2. dotnet build/run/watch work as expected
  3. Install VSCode, C#, and wasm debugging extensions and open the folder for the above
  4. It prompts to create debugging files, click Yes
  5. Press F5

Expected behavior: Opens the app and allows debugging, and allows debugging to stop

Actual behavior: Doesn't open the app (just a blank Chrome window) and ignores attempts to stop debugging

Additional context: Generated launch.json:

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch and Debug Standalone Blazor WebAssembly App",
            "type": "blazorwasm",
            "request": "launch",
            "cwd": "${workspaceFolder}/BlazorApp"
        }
    ]
}

uecasm avatar Mar 08 '22 00:03 uecasm

This appears to be related to #6072, which was closed as "fixed" but does not seem to be fixed...

uecasm avatar Mar 08 '22 00:03 uecasm

I have the same problem trying to debug blazor webassembly

Version: 1.65.2 (user setup) Commit: c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1 Date: 2022-03-10T14:33:55.248Z Electron: 13.5.2 Chromium: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.22000

NET SDK 6.0.100 C# v1.24.1 Microsoft.AspNetCore.Razor.VSCode.BlazorWasmDebuggingExtension v1.1.0

elgransan avatar Mar 15 '22 22:03 elgransan

FWIW, debugging does appear to work as expected in VS2022.

uecasm avatar Mar 16 '22 12:03 uecasm

Same issue here. Not being able to debug on vscode seems pretty big tbh.

DanielHazlewood avatar Jun 20 '22 10:06 DanielHazlewood

Hmm. Looks like this is due to vscode razor extension not being published in a while, I built a version locally off latest and I'm able to debug wasm now.

DanielHazlewood avatar Jun 20 '22 12:06 DanielHazlewood

The last publish of the Microsoft.AspNetCore.Razor.VSCode.BlazorWasmDebuggingExtension extension was in 05/21/2021, .NET 6 arrived in Nov/2021... there are any plans to update and publish the official extension?

gustavobigardi avatar Aug 09 '22 11:08 gustavobigardi