spikerj/spikersoft-issues
1
0 Fork 0
Code Issues 23 Pull Requests Actions Packages Projects Releases Wiki Activity

[Enhancement] C# playground: Monaco debugger toolbar — WASM + PDB (Blazor-class), breakpoints, stepping, vars #33

New Issue
Closed
opened 2026-04-28 23:15:56 +00:00 by spikerj · 1 comment
spikerj commented 2026-04-28 23:15:56 +00:00
Owner
Copy link
Copy source

Summary

Add a Monaco debugger toolbar to the C# playground, using the same class of .NET WebAssembly debugging stack Blazor WebAssembly relies on: IL execution in WASM with debugger hooks, Roslyn-compiled assemblies with symbols (PDB), mapper IL ↔ C# lines, UI-driven breakpoint / step-over / step-into / step-out / continue plus locals inspection.

Architectural outline (intent)

  1. Roslyn: compile user C# → IL + PDB (or equivalent symbol payload for WASM debugger consumption).
  2. Mono/.NET WASM runtime: execute IL inside the browser worker/runtime we already shell for grading/sandbox.
  3. Debugger bridge: debugger maps IL offsets → source locations → Monaco line/column; UI sends debugger commands (continue, single-step variants, breakpoints).

Toolbar — feature parity targets

  • Breakpoints (gutter bindings ↔ runtime).
  • Step over, step into, step out, Continue.
  • Variable inspection: locals / scoped names per paused frame.
  • Current line decoration in Monaco synchronized with paused IP.

Risks / notes

  • Bundle / load cost of PDB + WASM debugger components — document tradeoffs vs teaching-grade UX gains.
  • Align with app-language-runner / grading pipeline so debug mode does not weaken isolation or confuse “certified submit” semantics—clear mode separation (Debug vs Run/Grade).
  • Edge cases: partial programs, preprocessor-only files, deterministic project layout for PDB paths.

Acceptance criteria

  • User can set breakpoints and hit them in WASM execution path used by the playground.
  • Step commands wired to WASM debugger (not façade-only).
  • Monaco shows paused line + inspectable vars aligned with PDB mapping.
  • Document limitations (threads, unsupported constructs) for curriculum authors.

Related

  • #24 Monaco migration on app-language-runner; this ticket layers debugger on top for C# specifically.
## Summary Add a **Monaco debugger toolbar** to the **C# playground**, using the **same class of .NET WebAssembly debugging stack Blazor WebAssembly relies on**: IL execution in WASM with debugger hooks, **Roslyn-compiled** assemblies with **symbols (PDB)**, mapper **IL ↔ C# lines**, UI-driven **breakpoint / step-over / step-into / step-out / continue** plus **locals** inspection. ## Architectural outline (intent) 1. **Roslyn**: compile user C# → **IL + PDB** (or equivalent symbol payload for WASM debugger consumption). 2. **Mono/.NET WASM runtime**: execute IL inside the browser worker/runtime we already shell for grading/sandbox. 3. **Debugger bridge**: debugger maps **IL offsets → source locations** → Monaco **line/column**; UI sends debugger commands (**continue**, single-step variants, breakpoints). ## Toolbar — feature parity targets - **Breakpoints** (gutter bindings ↔ runtime). - **Step over**, **step into**, **step out**, **Continue**. - **Variable inspection**: locals / scoped names per paused frame. - **Current line decoration** in Monaco synchronized with paused IP. ## Risks / notes - Bundle / load cost of PDB + WASM debugger components — document tradeoffs vs teaching-grade UX gains. - Align with **`app-language-runner` / grading pipeline** so debug mode does not weaken isolation or confuse “certified submit” semantics—clear mode separation (**Debug vs Run/Grade**). - Edge cases: partial programs, preprocessor-only files, deterministic project layout for PDB paths. ## Acceptance criteria - [ ] User can **set breakpoints** and hit them in WASM execution path used by the playground. - [ ] **Step commands** wired to WASM debugger (not façade-only). - [ ] Monaco shows **paused line + inspectable vars** aligned with PDB mapping. - [ ] Document limitations (threads, unsupported constructs) for curriculum authors. ## Related - `#24` Monaco migration on `app-language-runner`; this ticket layers **debugger** on top for **C#** specifically.
spikerj commented 2026-08-07 13:50:02 +00:00
Author
Owner
Copy link
Copy source

Migrated to spikerj/spikersoft-angular#663 as part of the umbrella-tracker breakup.

Verified 2026-08-07 against spikersoft-angular@8e5a4048: no debugger toolbar/bridge/PDB emission in dev-tools-csharp-runner; JS and Python equivalents do exist and are the pattern to follow.

Status: not started — unblocked (Monaco #24 landed; JS/Python debugger toolbars already ship as precedent).

Closing here. Work now lives in the repo that holds the fix, so fixes #<N> in a PR will
auto-close it on merge. The umbrella tracker keeps cross-repo epics only.

— Opus 5 Agent

Migrated to **spikerj/spikersoft-angular#663** as part of the umbrella-tracker breakup. Verified 2026-08-07 against `spikersoft-angular@8e5a4048`: no debugger toolbar/bridge/PDB emission in `dev-tools-csharp-runner`; JS and Python equivalents do exist and are the pattern to follow. Status: not started — unblocked (Monaco #24 landed; JS/Python debugger toolbars already ship as precedent). Closing here. Work now lives in the repo that holds the fix, so `fixes #<N>` in a PR will auto-close it on merge. The umbrella tracker keeps cross-repo epics only. — Opus 5 Agent
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
agentic
Actionable surfaced by the agentic architecture & security review
 bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 epic
Cross-repo epic — children live in per-repo trackers
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 sonarqube
Code quality issue surfaced by SonarQube (bug / code smell)
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
spikerj (Joseph Spiker)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#33