1

I am new to Dynamics 365 and have just started learning it. I am looking for a developer toolkit for Dynamics 365 which is supported for VS 2019.

The below MS toolkit supports VS 2015 and not the higher versions. https://marketplace.visualstudio.com/items?itemName=DynamicsCRMPG.MicrosoftDynamicsCRMDeveloperToolkit&ssr=false#overview

While I could find some hacks to get it working for VS 2019 , I could not get it installed.

I tried following the steps mentioned here:(https://crmfortress.com/2017/06/02/dynamics-365-developer-toolkit-extensions-for-vs2017/) but no luck.

extension.vsixmanifest file contents: 

-->

I am getting this error:

This VSIX package is invalid because it does not contain the file extension.vsixmanifest at the root. The VSIX file may be corrupted.

(1) Can someone please suggest how do I get this working for VS 2019 ?

(2) If #(1) is not possible, can you please suggest a good alternative to the Microsoft Dynamics Developer toolkit which would work for VS 2019 ?

Thank you in advance.

user1685854
  • 13

1 Answers1

0

The following article contains the instructions: How to upgrade extensions to support Visual Studio 2019.

In short, you have downloaded the right software, but the extension.vsixmanifest file needs to be adapted to VS2019:

Here’s a version that support every major and minor versions of Visual Studio 14.0 (2015) and 15.0 (2017) all the way up to but not including version 16.0.

<Installation InstalledByMsi="false"> 
   <InstallationTarget Id="Microsoft.VisualStudio.Pro" Version="[14.0,16.0)" /> 
</Installation>

Simply change the upper bound of the version range from 16.0 to 17.0, like so:

<Installation InstalledByMsi="false">
    <InstallationTarget Id="Microsoft.VisualStudio.Pro" Version="[14.0,17.0)" />
    </Installation>
<Prerequisite>

Next, update the version ranges in the <Prerequisite> elements. Here’s what it looked like before:

<Prerequisites> 
   <Prerequisite Id="Microsoft.VisualStudio.Component.CoreEditor" Version="[15.0,16.0)" DisplayName="Visual Studio core editor" /> 
</Prerequisites>

We must update the version ranges to have the same upper bound as before, but in this case we can make the upper bound open ended, like so:

<Prerequisites> 
   <Prerequisite Id="Microsoft.VisualStudio.Component.CoreEditor" Version="[15.0,)" DisplayName="Visual Studio core editor" /> 
</Prerequisites>

This means that the Prerequisite needs version 15.0 or newer.

If you have a dependency on Microsoft.VisualStudio.MPF then delete it. This dependency is a legacy one that hasn’t been needed since before Visual Studio 2010. It looks something like this:

<Dependencies>
   <Dependency Id="Microsoft.VisualStudio.MPF.14.0" DisplayName="Visual Studio MPF" d:Source="Installed" Version="[14.0]" />
</Dependencies>
harrymc
  • 498,455