Power Platform ToolBox runs on Windows, Linux, and macOS, while XrmToolBox offers a much wider selection of plugins. We compare the architecture and capabilities of both tools, which support the development of Dynamics 365 and Power Platform applications.
Dynamics 365 and Power Platform developers use additional tools when the standard web interface does not provide the necessary settings or features. For many years, such extensions were developed primarily for XrmToolBox.
Power Platform ToolBox performs a similar function, but it was built using a different technology stack and runs on several operating systems. At the time of publication, however, it offered far fewer plugins than XrmToolBox.
Two toolkits for Microsoft app developers
The standard Power Platform Apps Maker portal allows you to build and extend applications based on Dynamics 365 and the Power Platform. However, some settings and configuration options are difficult or impossible to access through its interface.
The platform's community has developed many tools to make life easier for developers and those customizing low-code applications. Many of these tools function as plugins for XrmToolBox.
The Power Platform ToolBox also brings together such solutions, but it addresses the need for a modern, cross-platform environment.
Why was there a need to create the Power Platform ToolBox?
XrmToolBox has been in development for over a decade. Its user interface deviates from modern standards, and it runs only on Windows.
An application's performance and stability may also depend on the plugins running within it. The Power Platform ToolBox is designed to address these limitations and works on three systems:
- Windows,
- Linux,
- macOS.
This allows teams working on different operating systems to use it.
XrmToolBox Architecture
The older tool was built as a Windows Forms application running on the classic .NET Framework 4.8.
It uses the Managed Extensibility Framework (MEF) to support plug-ins. It also uses libraries designed for Windows, including those related to the user interface and connections to Dataverse.
Because it depends on these components, XrmToolBox cannot be run in environments other than Windows.
The Cross-Platform Design of Power Platform ToolBox
The newer application was written in TypeScript using the Electron framework. It uses IPC channels and a modular management pattern.
The architecture used makes it possible to develop versions for different operating systems. This is the main difference compared to a solution based on Windows Forms and Windows system libraries.
The plugin ecosystem for both tools
As of the date of publication, Power Platform ToolBox offered 18 plugins. XrmToolBox had over 100 available.
The number of extensions for the new platform may increase, but not all existing tools need to be migrated to it. Some may be discontinued or no longer actively developed.
In terms of the availability of extensions, XrmToolBox therefore still has a clear advantage.
Criteria for Selecting the Right Solution
When you work exclusively on Windows and access to a wide range of plugins is essential, XrmToolBox remains the solution with the larger ecosystem of extensions.
The Power Platform ToolBox is worth considering if the tool is also supposed to run on Linux or macOS, or if the team wants to use an application based on a newer technology stack.
The decision depends primarily on:
- operating systems used by the team,
- availability of the required plugins,
- tools needed to develop and configure Dynamics 365 and Power Platform applications.
Power Platform ToolBox provides a cross-platform environment, while XrmToolBox still stands out with a significantly larger number of available plugins.
Are you facing a similar challenge?
One email a month—just the facts
What's happening with Dynamics, Power Platform, and Copilot—without the marketing hype.