Skip to content
PhuocLe edited this page Jun 20, 2026 · 42 revisions

DynamicsCrm.DevKit is a toolkit for building Dataverse / Dynamics 365 solutions with a consistent project structure, generated code, deployment automation, and validation rules. It is designed for teams that work with plugins, workflow activities, Custom APIs, virtual table data providers, web resources, reports, tests, and solution packaging, and want those pieces to stay predictable across local development and automated environments.

The Visual Studio extension is the starting point for most developers. It creates the project and item templates used in a DevKit solution, generates server-side and client-side code, lets teams customize C# generation through T4 templates, and adds right-click commands for common actions such as deploying web resources or synchronizing CrmPluginRegistration attributes from Dataverse.

The CLI is the automation surface. Use it when the same work needs to run outside Visual Studio: generating code, deploying plugins and web resources, building models, downloading reports, packing solutions, or running compatibility commands for older DevKit workflows. The CLI also hosts the MCP server, so AI agents can inspect and operate against Dataverse through documented DevKit tools instead of ad-hoc scripts.

Around those two main surfaces, DevKit provides companion tools and analyzers. devkit-tool handles supporting tasks such as documentation generation, code documentation, coverage conversion, minification, entity scaffolding, and solution layer inspection. The analyzer package adds DEVKIT1001 through DEVKIT1021 rules to catch Dataverse-specific risks before runtime, including registration mistakes, unsupported images, expensive SDK usage, missing tracing, sandbox-blocked APIs, and unsafe plugin patterns.

Start with Install, Connection, and Configuration if this is your first time using DevKit. Use VSIX when you are creating or editing a solution in Visual Studio, CLI when you need repeatable automation, Tools for supporting utilities, and Analyzers when you want Dataverse rules enforced while coding. Tutorials show how these pieces fit together in real development scenarios.

Start Here

Page Use it for
Install Install the Visual Studio extension and prepare the local development environment.
Connection Configure Dataverse connection profiles used by the VSIX, CLI, and automation tasks.
Configuration Understand the solution-level DevKit configuration files used by generated projects.

Main Areas

Area What you will find
Tutorials Practical walkthroughs that combine templates, generated code, deployment, testing, and Dataverse configuration.
VSIX Visual Studio project templates, item templates, T4 template customization, and right-click commands.
CLI Command-line automation and MCP server documentation for repeatable local, CI, and AI-assisted workflows.
Tools Companion devkit-tool commands for docs, coverage, minification, entity scaffolding, and solution diagnostics.
Analyzers Roslyn diagnostics for Dataverse plugin, workflow, HTTP, SDK, tracing, image, and sandbox best practices.

VSIX Details

Page Use it for
Project Templates Choose the correct Visual Studio project type for shared code, server code, packages, web resources, tests, reports, and solution packaging.
Item Templates Add generated classes and files such as plugins, workflow activities, Custom APIs, data providers, tests, JavaScript, and TypeScript assets.
T4 Templates Customize generated C# item template code, including team-specific plugin frameworks and Package Project scenarios with NuGet dependencies.
VSIX Commands Understand Visual Studio context menu commands such as deploy web resource, deploy TypeScript release, and add CrmPluginRegistration.

CLI Details

Page Use it for
CLI Commands Learn the devkit commands for generation, deployment, model building, web resources, reports, solutions, and legacy aliases.
MCP Tools Browse the MCP tools hosted by the CLI for Dataverse-aware AI agent workflows.

Reference

Page Use it for
HowTos Short task-focused notes.
FAQ Common questions and answers.

For AI Readers

If an AI agent reads this Home page first, the most important next page is Wiki Map. It contains the complete list of wiki documentation links and should be used as the catalog for discovering all DevKit docs before answering project-specific questions.

Clone this wiki locally