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.
- Without a Browser, where does your code run? – Henk Holterman Commented Mar 24 at 3:53
2 Answers
Reset to default 1You 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
版权声明:本文标题:c# - Blazor WASM debugging break points does not work with launchBrowser false - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1744282071a2598699.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论