Skip to main content

Microsoft Dynamics 365 Developer Toolkit for Visual Studio 2017

Microsoft Dynamics 365 Developer Toolkit for Visual Studio 2017


If you are used to working with Microsoft Dynamics 365 Developer Toolkit in Visual Studio 2015 you will realize quickly that Microsoft didn’t provide a new version for Visual Studio 2017.
Here are step to take Microsoft Dynamics 365 Developer Toolkit for Visual Studio 2015 and make it functional for Visual Studio 2017
1.       Download Microsoft Dynamics 365 Developer Toolkit from here
2.       Uncompressed the .vsix and open folder
Locate extension.vsixmanifest


1.       Open in a text editor in my case I used Notepad and locate the following
<Installation>
    <!--<InstallationTarget Version="[11.0,12.0)" Id="Microsoft.VisualStudio.Pro" TargetPlatformVersion="4.0" />-->
    <InstallationTarget Version="[11.0,14.0]" Id="Microsoft.VisualStudio.Premium" />
    <InstallationTarget Version="[11.0,14.0]" Id="Microsoft.VisualStudio.Pro" />
    <InstallationTarget Version="[11.0,14.0]" Id="Microsoft.VisualStudio.Ultimate" />
  </Installation>
2.       Replace the 14 with 15
<Installation>
    <!--<InstallationTarget Version="[11.0,12.0)" Id="Microsoft.VisualStudio.Pro" TargetPlatformVersion="4.0" />-->
    <InstallationTarget Version="[11.0,15.0]" Id="Microsoft.VisualStudio.Premium" />
    <InstallationTarget Version="[11.0,15.0]" Id="Microsoft.VisualStudio.Pro" />
    <InstallationTarget Version="[11.0,15.0]" Id="Microsoft.VisualStudio.Ultimate" />
  </Installation>
3.       Save File
4.       Compress Folder



1.       And change the extension to .vsix




At this point you are ready to install.

Once you are done installing Open Visual Studio navigate to:

        Tools -> Options





















Navigate to Dynamics 365 Developer Toolkit -> Tool Paths



Do the following Mappings:
1.       Path to the Plug-in Registration Tool (version 8.1 +)
a.       Map it to the folder where your Plugin registration Tool resides
2.       Path to the Crm Sdk Directory (version 8.1 +)
a.       Map it to the folder where your sdk .dll files resides

Enjoy J

Comments

Post a Comment

Popular posts from this blog

How to Close/Resolve Case in Power Automate Flow

 How to Close/Resolve case from Power automate flow from your DataVerse Connector Add a New Row Table Name: Case Resolutions Subject: Add your subject here Case (Cases): incidents({Case Id Guid})

Azure DevOps Fork Repos between two Organization

  Azure DevOps Fork Repos between two Organization This weekend I embarked on a topic a bit foreign to myself, on the surface seemed a bit simple. The idea is to fork my Azure DevOps Repo to a different organization and push changes between them. Bad news DevOps doesn’t allow to fork Repos to a different organization, you have only the capability to fork to a different Projects within the same Organization. I’m pretty much sure there are so many other ways to solve this issue, but this is the one that I found to be easy to implement. Import Repo to the new Organization Remember here you have to generate a personal token to be able to import the Repo you have to be a member of the new organization as well This might take a few minutes depending on the size of your project, once its complete you will receive a confirmation email, or just refresh it after few minutes So far all looks good, you can clone the solution in your new Organizati...

Using Adaptive Cards on Power Virtual Agent

  Adaptive Card for Power Virtual Agent its on preview, this feature will enable you to enhance your bot with a better visual responses. Here is a demo of a Power Virtual Agent I have embedded on Teams Its quite easy to implement you can use Adaptive Card Designer to generate JSON for your Adaptive Card. You can start by selecting "Ask with Adaptive Card" Here will be able to configure You can Use Adaptive Card Designer for designing your Card, its quite easy to work with. If you are skilled developer you can take advantage of the JSON. This is your JSON template: {     "type" : "AdaptiveCard" ,     "$schema" : "http://adaptivecards.io/schemas/adaptive-card.json" ,     "version" : "1.5" ,     "body" : [] } T