umbraco-debugging
Installation
SKILL.md
Debugging
Two tools answer two different questions. Source Link lets your debugger load the PDBs Umbraco publishes and download the matching source from GitHub, so you can set breakpoints in and F11 into Umbraco itself. Debug mode + MiniProfiler shows where a request spends its time (your code, Umbraco's code, SQL) without attaching a debugger at all.
| A — Step into Umbraco source | B — Debug mode + MiniProfiler / IProfiler | |
|---|---|---|
| Reference | approach-a-sourcelink.md | approach-b-debug-mode-profiler.md |
| Answers | "What is Umbraco doing inside this call, and why?" | "Why is this page slow, and which step is it?" |
| Where it runs | Your local IDE, with the site launched under the debugger | Any non-production environment, in the browser |
| What changes | IDE settings only (Source Link, symbol servers, Just My Code, JIT). Nothing in the project | Umbraco:CMS:Hosting:Debug in environment config, plus optional IProfiler.Step calls in your code |
| Ships | assets/SourceLinkProbe.cs (an F11 target), assets/vscode-launch.json |
assets/ProfiledController.cs (nested IProfiler steps) |
Before answering or changing anything, open the reference for the approach you choose and start from its asset. The traps are covered only there: the per-IDE setting names, the symbol server that Source Link depends on, and how profiling is gated.