The Visual Studio 2022 add-in is now available for Dynamics 365 for Financials and Operations.

Peter Villadsen

TL;DR: The Dynamics 365 for Finance and Operations Visual Studio add-in is now available for use in Visual Studio 2022 (VS 2022).

Visual Studio 2022 is the first 64-bit version of Visual Studio. We wanted to take advantage of the stability it brought (and set us up for the future) and this gave us the opportunity to rework and rethink some of our code.

Image VS 2022 for d365fo
Visual Studio 2022 for D365 F&O


One of the big benefits of adopting this new 64-bit architecture is that it solves many of the issues that we have seen in debugging scenarios. Some of our packages are very big, and the memory pressure caused by loading the symbol files were causing some stability problems in the 32-bit architecture. We are happy to say that this new version has reduced these instabilities very significantly. However, we recommend that you still carefully manage the packages from which you load the debug symbols: Always use the PDB files that we ship with the product (rather than building them yourself) because the shipped PDB files are much smaller than the ones you can create locally. These efforts are still worth doing, since they pay dividends in the time spent loading the PDB files.

How to get it

The new VS 2022 add-in is installed on the VHDs environments (the October release, with the PU61 / App payload) that you can download from LCS. If you have an environment hosting VS 2019, you can go ahead and install Visual Studio 2022 (from here: Visual Studio 2022 IDE – Programming Tool for Software Developers). Your next deployment will install the VS 2022 VSIX, starting from PU 60.

If you are using the Unified Developer Experience, you can download the Power Platform VS extension from the Visual Studio Marketplace through the VS 2022 application. When you connect to the Dataverse environment, you will get the extension downloaded.


Discussion is closed. Login to edit/delete existing comments.

  • James Majcen 0

    Thanks Peter. Which VSIX should we be installing for the tooling? There is Microsoft.Dynamics.Framework.Tools.InternalDevTools.17.0.vsix and Microsoft.Dynamics.Framework.Tools.Installer.17.0.vsix and both list VS2022 as an installation target.

    • Paul Heisterkamp 0

      Microsoft.Dynamics.Framework.Tools.InternalDevTools.17.0.vsix has always been only for internal use, inside Microsoft.

Feedback usabilla icon