How It Works
How It Works
Section titled “How It Works”XrmGhost moves the first validation step for Dataverse plugins from the cloud to your machine. Instead of deploying every change just to see whether the code behaves correctly, you run the plugin locally against a controlled scenario and inspect the result immediately.
The local-first model
Section titled “The local-first model”At a high level, the workflow looks like this:
- You prepare a plugin project and the scenario you want to run.
- The XrmGhost CLI starts the workflow from your terminal or automation.
- The local host executes plugin logic in a runtime shaped to match Dataverse expectations.
- You inspect the outcome, adjust code or inputs, and rerun within seconds.
This keeps development feedback close to the code while still reflecting the server-side plugin model you ultimately deploy to Dataverse.
Core components
Section titled “Core components”| Component | Role |
|---|---|
| CLI | The main developer entry point for setup, execution, diagnostics, and scenario workflows. |
| Framework host | The local execution process that mirrors the .NET Framework runtime expected by Dataverse plugins. |
| Scenario and environment inputs | The configuration and test data that make runs reproducible. |
What this changes for teams
Section titled “What this changes for teams”The value is not just speed. The model also improves how teams work:
- Shorter feedback loops because you do not need a deployment for every code check.
- Repeatable investigation because a scenario can be rerun instead of rebuilt manually.
- Clearer cloud validation because deployment can focus on final confirmation and integration.
Where to go next
Section titled “Where to go next”- Start with Overview if you need the product-level context.
- Continue to Getting Started if you want to install the tooling.
- Review Editions for the Standard and Pro editions.
- Use CLI for command-level detail.