Dataverse: Build D365 Plugins in VS Code

Key insights

• Dataverse plugin development in this YouTube video shows how to write and deploy plugins using VS Code instead of Visual Studio.
  The presenter explains the full lightweight workflow for Dataverse (Dynamics 365) plugins.
• Required setup: install Power Platform CLI and the Dataverse DevTools extension in VS Code.
  The video also covers signing into your environment and using commands like pac plugin init to scaffold projects.
• Coding options: write plugin logic in C# or TypeScript with generated typings for IntelliSense.
  The speaker shows how the extension adds code completion and type safety for Dataverse entities.
• Build and deploy: compile assemblies with MSBuild or CLI tools, then register or update them using the Plug-in Registration path in the Power Platform tools.
  The video explains packaging, uploading, and replacing assemblies from VS Code.
• Productivity benefits: the approach is lightweight, supports fast iteration, and removes the need for a heavy IDE.
  The presenter highlights quicker feedback, easier testing, and built-in web resource and connection management.
• New capabilities: integration with Model Context Protocol (MCP) and the ability to compile Power FX into C# are covered as modern advances.
  The video shows how these features improve code suggestions and let low-code logic run as native plugin code.

Sean Astrakhan of Untethered 365 published a YouTube video that walks through a modern way to write Dataverse (Dynamics 365) plugins using VS Code rather than the full Visual Studio IDE. In his coverage, he draws on a blog post by Richard Carrigan and highlights how Microsoft and the community now enable plugin development with lightweight editors, the Power Platform CLI, and the open-source Dataverse DevTools extension. Consequently, the video frames this shift as a practical and faster option for developers who prefer streamlined tools. Moreover, it explains the steps to scaffold, build, and deploy plugins while pointing out the new language and tooling options available in 2025.

What's changing in Dataverse plugin development

First, the video emphasizes that creating Dataverse plugins no longer requires installing Visual Studio Community or other heavyweight IDEs. Instead, developers can use VS Code combined with command-line tooling to manage projects, build assemblies, and register plugins directly to a Dataverse environment. Furthermore, the integration of the Power Platform CLI and the Dataverse DevTools extension brings connections, scaffolding, and code generation inside the lightweight editor for a smoother workflow.

In addition, the video covers newer capabilities like compiling Power FX into C# and experimenting with the Model Context Protocol for improved editor assistance and GitHub Copilot-style suggestions. Therefore, developers gain more language choices and smarter code help while building server-side logic. However, the video also notes that not every legacy feature from full Visual Studio maps perfectly to the new setup, so adoption involves tradeoffs.

Tools and setup demonstrated

Astrakhan walks viewers through installing essential pieces: VS Code, the Dataverse DevTools extension, and the Power Platform CLI. After that, he shows authenticating to a Dataverse environment and managing those connections within the editor, which simplifies switching contexts during development. Additionally, he demonstrates initializing a plugin project with commands such as pac plugin init and creating TypeScript or C# project scaffolds that include typings and boilerplate logic.

He also covers building and packaging steps using CLI-driven routines and how to use the plug-in registration workflow through integrated tools or the classic registration utility. Consequently, the process becomes more scriptable and repeatable, which helps teams automate deployments in CI/CD pipelines. Yet, the video warns that teams must still configure MSBuild, signing, and packaging correctly when moving from a local demo to production scenarios.

Workflow and developer experience

The video praises the faster iteration cycle when developers use VS Code with typings and editor intelligence, which delivers improved autocompletion and earlier error detection. Moreover, Astrakhan demonstrates how to upload web resources, generate TypeScript definitions for entities, and debug logic with immediate feedback from the environment. This improved loop helps small teams or individual contributors move quickly from idea to working plugin.

Nonetheless, Astrakhan points out that advanced Visual Studio features—such as integrated designers, deep enterprise debugging tools, and certain project templates—may still be richer in the full IDE. Therefore, teams must weigh the benefits of a lightweight, flexible editor against potential limitations in complex debugging or established enterprise workflows. In short, productivity gains may require reworking some existing processes.

Tradeoffs and practical challenges

The video clearly discusses tradeoffs between simplicity and completeness. On one hand, using VS Code and CLI tools reduces setup time, lowers resource use, and encourages automation; on the other hand, teams lose some of the GUI-driven tooling and integrated project controls that Visual Studio provides. Additionally, compiling Power FX into C# lowers the bar for non-developers to express logic, but it can make debugging and fine-grained performance tuning harder compared with hand-crafted C# code.

Astrakhan also addresses operational challenges: managing secure connections, handling signed assemblies, and ensuring consistent packaging across environments remain responsibilities that require clear processes. Consequently, adopting the new approach often means investing in CI/CD, good documentation, and standards for registration and versioning. Ultimately, the video urges teams to pilot the workflow and to document gaps before migrating large legacy codebases.

What this means for developers and teams

In conclusion, the YouTube video by Sean Astrakhan presents a practical path for many developers to build Dataverse plugins using modern, lightweight tooling. Moreover, it highlights how Microsoft and the open-source community have bridged gaps with the Power Platform CLI and Dataverse DevTools, enabling faster iteration and multi-language options. However, the video balances enthusiasm with realism by showing where established Visual Studio features still matter and by discussing the operational work needed for secure, repeatable deployments.

For newsrooms and development teams alike, the takeaway is clear: choose the toolchain that best fits your team’s size, complexity, and governance needs, and plan migration in stages. Consequently, the approach shown by Astrakhan can speed up many projects, but teams must manage the tradeoffs and invest in automation and testing to make the new workflow robust for production use.

Keywords

Write Dataverse D365 plugin VS Code, Dataverse plugin development VS Code, Dynamics 365 plugin VS Code tutorial, D365 plugin without Visual Studio, Build Dataverse plugin using VS Code, C# Dataverse plugin VS Code, Dataverse plugin debugging VS Code, VS Code Dynamics 365 plugin setup