Visual Studio 2019 is now available for developers and dynamics 365 CE version 9.x Software Development Kit (SDK) too. However Dynamics 365 Developer Toolkit only supports for Visual Studio 2012, 2013, 2015 and it uses Dynamics 365 CE SDK 8.x assemblies and tools.
This article to make Dynamics 365 Developer Toolkit workable for VS 2019 and to prevent some common issues when setting up Plugin Library project to work with Dynamics 365 CE version 9.x core assemblies.
Special thanks to Sucheet Chavan for sharing useful information to the article.
Setting up Developer Toolkit for VS2019
Although Dynamics 365 Developer Toolkit doesn’t support after Visual Studio 2015, developers perform few workarounds to use the extension with VS2017. Following article is still valid for VS2019 with one change to the extension.
Microsoft Dynamics 365 Developer Toolkit and Dynamics CRM & 365 Developer Extensions are great Dynamics 365 development accelerators available in the Visual Studio Marketplace. Still, these tools are not compatible with Visual Studio 2017, which is the latest release of VS. This is a workaround that you can make use of these tools with Visual Studio 2017.
Dynamics 365 Developer Extensions is a great replacement for Dynamics 365 Developer Toolkit, steps of the workaround has been given below for both the tools.
Step 1: Download Toolkit or Extensions from following links.
Microsoft Dynamics 365 Developer Toolkit
Dynamics CRM & 365 Developer Extensions
Step 2: Extract the .vxis file as follows.
Extracting Microsoft Dynamics 365 Developer Toolkit vsix file
 Download XrmPage-vsdoc.js from HERE
 Add XrmPage-vsdoc.js in to the Visual Studio IDE
Not like in most of the other developments, in Plugins developers have to debug the CRM plugin code at the time of running the application. Developers writing the plugin code inside the plugin and some times the logic can be write in a seperate assembly and from the plugin code it can be invoked. When writing the whole logic inside the plugin is little complex to test the plugin logic by debugging the plugin as it executes from the application itself in a given event such as create an entity, update or delete.
There are two ways of debugging a CRM plugin as follows,
 Attaching the debugger to the w3p.exe process
 Forcing the add-in to call the debugger
A plugin has written targeting Account entities as follows and a step has registered to be fired on Account entity’s Create step.
Type “regedit” on run and find follwing;
Add new String value to Text Editor and name it as “Guides”
Enter its value as “RGB(204,204,204) 99”
Visual Studio 2008 Text Editor looks like this;