Blazor WebAssembly custom debugger configuration

[Bradtus]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Since upgrading Visual Studio to 17.8 custom debug configurations for Blazor WASM can't debug anymore by default. The default Debug profile works fine though. It also works as expected for ASP.Net Core Web App Razor.
Only for Blazor WASM in the output i get the message "DEBUGGING IS NOT ENABLED" and breakpoints are unbound.
When adding <DebuggerSupport Condition="'$(Configuration)' == 'DebugCustom'">true</DebuggerSupport> it works again.

Expected Behavior

Debugging should be enabled by default on debugging profiles.

Steps To Reproduce

• Fresh install Visual Studio
• Create a new Blazor WASM project
• Create a new DebugCustom profile based on the default Debug profile
• Debug in Chromium using the DebugCustom profile

Exceptions (if any)

When pressing shift+alt+d => Cannot start debugging, because the application was not compiled with debugging enabled.

.NET Version

.net7.0 and .net8.0

Anything else?

cc: @guardrex dotnet/AspNetCore.Docs#31281

[guardrex]

Thanks @Bradtus.

@javiercn ... I thought DebuggerSupport was enabled by default for non-Release builds (or perhaps specificually for Debug builds). We only ever had one remark on it that you could enable it manually for a Release build if testing locally to enable debugging for a production build. We just lost that remark when we dropped coverage for hosted WASM. It occurs to me now that we probably should've had that for all Blazor apps (Server, WASM, hosted WASM) of <8.0. Anyway, we currently have no coverage on it for >=8.0. Therefore as part of addressing this issue, I'm 👂 to find out what you'd like to cover.

UPDATE: It was even more specific than I recalled ... the coverage was only for VSC debugging of hosted WASM (IIRC with Safia's help) ...

https://learn.microsoft.com/en-us/aspnet/core/blazor/debug?view=aspnetcore-7.0&tabs=visual-studio-code#debug-a-hosted-blazor-webassembly-app-in-an-ide

In any case, I'm 👂 for whatever you want to cover and will try to address it soon, but note that I'm still ⛰️⛏️😩 on many 8.0 doc issues. I'll get to it as soon as I can.

[ghost]

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Since upgrading Visual Studio to 17.8 custom debug configurations for Blazor WASM can't debug anymore by default. The default Debug profile works fine though. It also works as expected for ASP.Net Core Web App Razor.
Only for Blazor WASM in the output i get the message "DEBUGGING IS NOT ENABLED" and breakpoints are unbound.
When adding <DebuggerSupport Condition="'$(Configuration)' == 'DebugCustom'">true</DebuggerSupport> it works again.

Expected Behavior

Debugging should be enabled by default on debugging profiles.

Steps To Reproduce

• Fresh install Visual Studio
• Create a new Blazor WASM project
• Create a new DebugCustom profile based on the default Debug profile
• Debug in Chromium using the DebugCustom profile

Exceptions (if any)

When pressing shift+alt+d => Cannot start debugging, because the application was not compiled with debugging enabled.

.NET Version

.net7.0 and .net8.0

Anything else?

cc: @guardrex dotnet/AspNetCore.Docs#31281

Author:	Bradtus
Assignees:	-
Labels:	area-Debugger-mono
Milestone:	-

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Since upgrading Visual Studio to 17.8 custom debug configurations for Blazor WASM can't debug anymore by default. The default Debug profile works fine though. It also works as expected for ASP.Net Core Web App Razor.
Only for Blazor WASM in the output i get the message "DEBUGGING IS NOT ENABLED" and breakpoints are unbound.
When adding <DebuggerSupport Condition="'$(Configuration)' == 'DebugCustom'">true</DebuggerSupport> it works again.

Expected Behavior

Debugging should be enabled by default on debugging profiles.

Steps To Reproduce

• Fresh install Visual Studio
• Create a new Blazor WASM project
• Create a new DebugCustom profile based on the default Debug profile
• Debug in Chromium using the DebugCustom profile

Exceptions (if any)

When pressing shift+alt+d => Cannot start debugging, because the application was not compiled with debugging enabled.

.NET Version

.net7.0 and .net8.0

Anything else?

cc: @guardrex dotnet/AspNetCore.Docs#31281

Author:	Bradtus
Assignees:	-
Labels:	arch-wasm, untriaged, area-Debugger-mono
Milestone:	-

[maraf]

Before .NET 8, Blazor for setting DebuggerSupport=false for all non-Debug configurations, but was starting the runtime in the browser with debugging enabled for all builds (regardless of configuration). In .NET 8 we have unified the behavior: if DebuggerSupport=false the runtime starts without debugging; if DebuggerSupport=true runtime starts with debugging.

I'm not sure yet if the DebuggerSupport=false & debugging enabled makes debugger work properly in all situations

---

More notes

.NET 7

• debugBuild = 1 for build; 0 for publish
• hasDebuggingEnabled: hasReferencedPdbs || debugBuild
• debugLevel: hasDebuggingEnabled() ? 1 : 0
• DebuggerSupport: false for config!=Debug
• Summary
  • DebuggerSupport didn't affected wasm debugging, just instrumented linker
  • Debugging always fully (1, not -1) enabled for all builds, no way to turn it off
  • Debugging disabled for publish, but could be enabled with CopyOutputSymbolsToPublishDirectory=true (and DebuggerSupport=true just to instrument linker)

.NET 8+

• debugLevel = -1 for Configuration==Debug or DebuggerSupport==true; 0 otherwise
• hasDebuggingEnabled: hasReferencedPdbs || debugLevel != 0
• debugLevel: hasDebuggingEnabled() ? debugLevel : 0

Solution

• Enable debugging when DebuggerSupport==true
• Enable debugging for all builds until WasmDebugLevel==0 set by user
• Disable debugging for publish until CopyOutputSymbolsToPublishDirectory=true or WasmDebugLevel!=0 set by user
• On runtime debugLevel = (debugLevel != 0 || hasPdbs) && supportedBrowser ? 1 : 0 ??

TODO

• Check publish with DebuggerSupport=true in .NET 7 SDK => No pdbs and debugBuild=0