I am trying to debug a Blazor Webassembly (5.0.1) application in VS 2019 via attaching the debugger to Chrome - I can't use "direct" debugging from VS because I have a modular project structure with multiple "modules" (RCLs) placed in different VS solutions
What I tried so far:
- setting up an own IIS: Debugging ASP.NET Core applications running in IIS
- starting Chrome with remote debugging port cmd: chrome --remote-debugging-port=9222
When attaching VS 2019 to Chrome, the Console.WriteLines() will show in VS output window, but no breakpoints are hit (no symbols loaded) - the "mono_wasm_runtime_ready" also shows up in the output.
When publishing, i tried with "debug" configuration, as well as "BlazorEnableCompression" set to false - nothing worked so far.
(I tried this with the default blazor-webassembly project template, also didn't work)
What am I missing? How can this be done?