Install Dynamics 365 Developer Toolkit with Visual Studio 2017

Visual Studio was officially released today, and with it’s release comes the dilemma for Dynamics 365 developers. Do you keep going with VS 2015 (or maybe VS2013, VS 2012 or 2010!), or do you bite the bullet and install Visual Studio 2017?


In the past, I would normally hold off on a new Visual Studio installation until there is a service pack available, but after reading that Visual Studio 2017 is focused on performance improvements and speed, I decided to install it on an Azure Developer VM to see if I could get the Dynamics 365 Developer toolkit working on it.

Microsoft Developer toolkit for Dynamics 365 / CRM has traditionally lagged behind Visual Studio in terms of releases, but with a few tweaks, it’s possible to get it up and running.

Step 1 – Download the VSIX for Dynamics 365.

This can be downloaded from here. Save it somewhere locally.


Step 2 – Extract the VSIX.

The VSIX is an archive. We need to update a file in there to get it to install. My tool of choice for doing this is 7zip. Right click and extract to a subfolder.


Step 3 – Update the VSIX Manifest

With a text editor, update the extension.vsixmanifest file. The existing VSIX will only work up to Visual Studio 2015 (14.0), so you need to update the references from version 14 to version 15. Once complete as shown below, save the file.


Step 4 – Install the VSIX

Because the VSIX was compiled by and for VS 2015, you will get a warning when installing, but it should still install successfully. We won’t be able to get rid of this warning, but just click OK, close and Restart Visual Studio.



Step 5 – Set your  Dynamics 365 SDK Paths in Visual Studio

If you haven’t already installed the SDK, download and extract it now. Then go to Tools -> Options -> Dynamics 365 Developer Toolkit -> Tool Paths. Set the paths to point to the plugin registration tool folder and bin folder where you extracted your SDK.


Step 6 – Update the Toolkit dlls with more recent versions from the SDK (Optional)

To avoid some connectivity issues with the Developer Toolkit, I found by replacing the embedded SDK dlls which have an older version than those in the current Dynamics 365 SDK it worked fine. You can do this before installing by updating the packed VSIX and reinstalling. Alternatively you can update post-install by looking for and updating the dlls in the folder C:\Users\<user>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\<pluginid>

Update these libraries :

As Microsoft appear to be providing updates to this toolkit more frequently than in the past, I would be inclined to only update these DLLs if you run into connectivity problems after installing.

So far so good for me – I have successfully connected to both CRM 2016 and 365 on-premise and online instances.

Good luck!

This entry was posted in Dynamics 365, Uncategorized and tagged . Bookmark the permalink.

16 Responses to Install Dynamics 365 Developer Toolkit with Visual Studio 2017

  1. Pingback: Hosk’s Top Dynamics 365 Articles of the week – 31st March – Hosk's Dynamic CRM Blog

  2. Pingback: Hosk’s Top Dynamics 365 Articles of the week – 31st March - Microsoft Dynamics CRM Community

  3. Alex says:

    anyone also got this error with Workflow Project: HRESULT: 0x80070057 (E_INVALIDARG))

  4. Shobhit Saxena says:

    Its not working for me. How can we make sure that after editing the contents of the xml file, the same are reflected back to the setup file which we extracted ?

    • Did you ever get this to work? I feel like there’s a step missing – How do you repackage the contents into an installer again? I tried zipping it back up but the installer gives an error saying it’s not a valid VSIX package.

      • brianilland says:

        Yes, you will need to replace the xml file in the vsix zip with the modified one. There are a few different ways to do this.

        For example, you could just rename the file from .vsix to Then use windows explorer to copy it to your desktop and update it, and then drag it back into the zip file.

        Once finished rename the file back to .vsix and double click to install.

  5. Tayyaba Gouhar says:

    Don’t extract the folder instead open the archive using 7-zip and edit & save extension.vsixmanifest file as mentioned above.

  6. Eiwan Koh says:

    Successfully installed! Extract file and edit the .vsixmanifest then open archive Microsoft.CrmDeveloperTools using 7-zip drag the edited .vsixmanifest to opened Microsoft.CrmDeveloperTools.

  7. Joe says:

    Where can I download Dynamics 365 for Operations and Finance template without LCS?

  8. Bhautik says:

    Is anyone facing issue to update webresource ? I am unable to publish webresource to the CRM as the publish button is disabled.

  9. Luke says:

    Is anyone having issues connecting to on-prem CRM 2015 from Visual Studio 2017?

  10. It may install but the project templates are unsupported, will need to wait for full I suppose 😦

  11. Ligh Wind says:

    I did not unzip the file, but open the archive and edit the Manifest file as indicated, then install. It works as suggested. Thank you!

  12. How did you open the archived file and make the edit. When I’m clicking open, it starts executing the file.

  13. santiago says:

    Where is Manifest? I don’t know witch is extraction path. can you help me? Thanks for your article!!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s