admin管理员组

文章数量:1401842

I disabled launchBrowser via the launchSettings.json file, and now the breakpoints are not active, it says

The breakpoint will not currently be hit. No symbols have been loaded for this document

If it change launchBrowser back to "true", debugging works fine.

I disabled launchBrowser via the launchSettings.json file, and now the breakpoints are not active, it says

The breakpoint will not currently be hit. No symbols have been loaded for this document

If it change launchBrowser back to "true", debugging works fine.

Share Improve this question edited Mar 23 at 15:47 marc_s 756k184 gold badges1.4k silver badges1.5k bronze badges asked Mar 23 at 14:57 RichardRichard 213 bronze badges 1
  • Without a Browser, where does your code run? – Henk Holterman Commented Mar 24 at 3:53
Add a comment  | 

2 Answers 2

Reset to default 1

You may read this document

The inspectUri property:

  • Enables the IDE to detect that the app is a Blazor app.

  • Instructs the script debugging infrastructure to connect to the browser through Blazor's debugging proxy.

The placeholder values for the WebSocket protocol (wsProtocol), host (url.hostname), port (url.port), and inspector URI on the launched browser (browserInspectUri) are provided by the framework.

The browser has to be launched to provide inspector URI

You may try to manually attaching the debugger or tweaking the launchSettings.json file should resolve the "No symbols loaded" error.

本文标签: cBlazor WASM debugging break points does not work with launchBrowser falseStack Overflow