Aspnetcore: Debugging

[danroth27]

• [ ] Debug server

[Thaina]

Doesn't this worked?

https://twitter.com/davidfowl/status/891125650286755840

[RyoukoKonpaku]

@Thaina I think that example was based on the old Blazor version before the ASP.NET team re-wrote it to what you see today. So I doubt that debugging feature is gonna work now.

[Thaina]

Maybe we should ask @davidfowl

Sorry for bother you

[danroth27]

Correct, debugging has yet to be implemented with the new code base.

[ericgrantholland]

Looks like server-side debugging is working. What about debugging client-side in the functions area? Is this planned to be supported in the future?

[SteveSandersonMS]

Since work on this is now underway in the Mono repo, and we've already integrated Blazor with that, I think this issue is no longer tracking anything so I'll close it.

[janaka]

Can you clarify if debugging client side works? Particularly interested in VS Code.

[ericgrantholland]

Client-side debugging does work in chrome after a few annoying steps. The official write-up for it is actually really good. See below

https://blazor.net/docs/debugging.html

[didii]

So how does one exactly debug? I've followed the steps from the guide (https://blazor.net/docs/debugging.html) but I'm facing some issues:

• Alt+Shift+D does nothing
  
  
  
  • I can circumvent this by manually going to http://localhost:9222 and selecting the correct window
  
  
• After loading into the inspector view, no .dll show up in the file list so I can't set any breakpoint

Steps I took:

1. Build the solution in Debug
2. Open chrome with %programfiles(x86)%\Google\Chrome\Application\chrome.exe --remote-debugging-port=9222 http://localhost:52734
3. Open a new tab in chrome and navigate to localhost:9222 and select the window where the blazor app is running in
4. In the tab sources the .dll is not visible (after refreshing the app, the entry wasm appears, but seems to contain only IL-like code)

Should I open a new issue for this? Can't find anything related to my current problem.

[Gnredwards]

@didii I experienced a similar issue, in the end the problem was cause because I'm using an alternative keyboard layout (Dvorak). Hitting what I thought was Alt + Shift + D did nothing (this is Alt + Shift + H on a Qwerty keyboard). When I tried using the "real" D key it worked. Hope this may be of some use.

[didii]

@Gnredwards thanks. I just solved it myself yesterday evening. I simply had an extension that used that same keyboard shortcut and blocked Blazor from doing anything. So after disabling it, it worked!