Debugging Plugins: document running replays on .NET 8 (no .NET Framework needed)
Only the DEPLOYED plug-in assembly has to target .NET Framework — the copy the tests
run against does not, and the replay harness uses nothing Framework-specific. Verified:
the shipping harness replays a real captured profile under net8.0 on Linux.
Adds the multi-targeting recipe, with its caveats, and links the three places that
previously said 'Windows or mono' full stop. Tracked for the scaffolder in #269.
Profiling: capture is cross-platform from 1.0.7; be precise about what still needs .NET Framework
Capturing a plug-in profile no longer uses a bundled .NET Framework helper — the
extension starts and stops profiling over the Web API — so the Windows-only framing
across these pages was wrong.
Also corrects a claim that was never right: Requirements said replaying a run under
the debugger 'works everywhere'. The generated test lives in a plug-in test project
targeting net471, so dotnet build compiles it anywhere but dotnet test needs the
Framework test host (on Linux it aborts with "Could not find 'mono' host"). That is
now stated once, precisely, on each page that mentions it.
Adds what capture actually does — clone the step, move its images, disable the
original — since that explains both why naive Web-API step edits never fired it and
why a step can be left disabled if a session is interrupted.
Add FetchXML Generator, PCF, Custom APIs, Copilot tools and multi-component guides (#233)
Five pages the wiki had no coverage of at all, each a step-by-step guide rather than a feature list:
FetchXML Generator — why it works on the literal in your code instead of a separate file, the lens,
answering for placeholders, the results view, the generator, and what "Save to code" guarantees.
Five screenshots from the e2e suite driving the real UI.
PCF Controls — the Field/Dataset and None/React choices and what they mean, the eight card actions,
and when to use the harness versus debugging the deployed control on a live form.
Custom APIs — definition-as-code, generating the handler and the typed client, what the deploy
reconciles, and two honest caveats: Run Custom API is Global-binding-only, and the deploy's
create/update/delete calls are not yet verified against a live environment.
Copilot tools — the five tools, the read-only default, the per-call confirmation, and that no tool
output can carry a secret.
Multi-component repos — what makes a component, why the root owns the connection, how a command
picks its target, and the trap of pasting a connection into a subfolder (it stops following the
root).
Corrections to existing pages: legacy plugin support was removed in 1.0.3 (three pages still promised
"removed in 0.9.0"); the one Windows-only feature is profile CAPTURE, not the spkl path; and the replay
does not use the profiler's assemblies — it decodes the profile with Microsoft.Xrm.Sdk alone, which is
what lets it run in CI.
Add a step-by-step "Profiling a Plug-in Run" walkthrough with screenshots
Covers the whole capture → download → replay loop, with the button, dialog or
picker used at each step outlined in the screenshot. Both ways of choosing which
step to profile are documented: the panel's Profile next run, and the per-step
Profile CodeLens on the [CrmPluginRegistration] attribute.
The frames are captured by the end-to-end suite while it drives the real UI
(DVPT_E2E_SHOTS=1), so they cannot drift from the product without the suite
noticing. The org name and URL are redacted.
Two current limitations are stated rather than glossed over: stopping profiling
from the Profile: On lens does not work (pete-mc/dataverse-powertools#251, use the
Active profiles list), and Run/Debug Test at Cursor plus gutter icons do not work
for plug-in tests (pete-mc/dataverse-powertools#252, use the Testing view).
Linked from the sidebar and from Debugging Plugins.
Debugging-Plugins: refresh demo GIF (real in-process replay running green) + alt text (#138)
Debugging Plugins: add slideshow GIF + function screenshots (#136/#138)
Adds a plugin-debugging slideshow GIF at the top and per-function screenshots
(Profile & Debug CodeLens, generated replay test, rendered trace log), captured
from the UI against a demo (contoso) connection.
Expand Debugging Plugins: prerequisites, trace logs (#137), recommended route, troubleshooting (#136)
Adds the structure #136 asks for, grounded in the shipped code: a dedicated
Prerequisites section, the Trace logs diagnostic (org-header pill + Set/View
Plugin Trace Log commands from #137), a recommended-route callout per OS, and a
Troubleshooting table. Screenshots remain the only live-env-gated part.
Debugging Plugins: add overall-process mermaid diagram (#136)
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Debugging Plugins: capture is now one-click in-extension on Windows (Profile next run); PRT capture only on other OSes
Add Debugging Plugins guide (capture in PRT, download + replay-to-debug in VS Code)