#VSIT Can I include Visual Studio Integration Toolkit with my installer?

David Meego - Click for blog homepageSince the change from Menus for Visual Studio Tools to Visual Studio Integration Toolkit (VSIT) and more recently the release of Build 11 of Visual Studio Integration Toolkit, I have received some questions about how to include the VSIT code in the Visual Studio Tools Addin’s installer.

With the release of Build 11 of Visual Studio Integration Toolkit for GP 2010, GP 2013, GP 2015 and GP 2016, the product now has a full installer and registration system. The registration system was added to allow tracking of the usage of the tool for support purposes and to justify continued development. The installer was added because it is more professional and it is required to get the addin DLL files and registration system installed correctly.

A few questions have been raised after these changes. Below are some of the questions and their answers:

I used to include the DLL and CNK files in my installer, can I still install VSIT this way?

No, you cannot just include the files in your installer as there are registry changes also needed now.

Is there a way to avoid having to install VSIT separately?

Yes, All Winthrop products support a silent install and can be installed silently by your installer.

Note: Including the VSIT installer file in your installer does mean that you might not have the latest code. If you can download the installer first, then install it that is even better.

How can I do a Silent Install of Visual Studio Integration Toolkit?

The Visual Studio Integration Toolkit installer supports a silent install with the appropriate parameters passed to the EXE file.

Below are examples of the syntax:

Installing to default instance of Microsoft Dynamics GP
IntegrationToolkit_14.00.0011.exe /s INSTALL=TRUE TARGETDIR="C:\Program Files (x86)\Microsoft Dynamics\GP2015\"
Installing to default instance of Microsoft Dynamics GP specifying instance name
IntegrationToolkit_14.00.0011.exe /s INSTALL=TRUE TARGETDIR=" C:\Program Files (x86)\Microsoft Dynamics\GP2015\" DYNINSTDESC="(Default)"
Installing to a specified instance of Miicrosoft Dynamics GP
IntegrationToolkit_14.00.0011.exe /s INSTALL=TRUE TARGETDIR=" C:\Program Files (x86)\Microsoft Dynamics\GP2015R2\" DYNINSTDESC="GP2015-R2"


  • The top two examples are essentially the same, if using the default instance of Microsoft Dynamics GP, then you don’t need to specify the instance name. If you do wish to specify the instance name then use “(Default)” for default instance.
  • When specifying the instance, it must match an existing GP instance as it will be checked in the registry.
  • When specifying the path, it must contain a Dynamics.exe of the same version as it will also be checked.

Does Visual Studio Integration Toolkit require registration for every customer?

Yes, the registration is required for every customer site, but it is free of charge for the base VSIT functionality.

Does the customer have to enter the registration keys into VSIT?

No, the keys will automatically be downloaded from the internet as long as the customer has been registered with Mekorma. You can still manually enter them, but that should not be needed as long as the system has an internet connection.

Does the customer have to organise the registration with Mekorma?

No, the developer or partner can organise the registration with Mekorma on behalf of the customer. Please email sales@Mekorma.com for more information.

As a developer or partner, do I have to register my development system?

Yes, you will need NFR (Not For Resale) registration keys. Please email sales@Mekorma.com with the following details:

  • Contact Name
  • Company Name
  • Company Address
  • Phone Number
  • Your Microsoft Account Number

Will there be a charge for Visual Studio Integration Toolkit in the future?

There are no plans to charge for the base functionality it already has. This is Winthrop’s and Mekorma’s gift to the Dynamics GP community.

However, at some time in the future, there are plans to add additional advanced features to the product and these will require a separate chargeable registration.


For more information, check out:


I hope that answers all the questions.

Thanks for your support


This article was originally posted on http://www.winthropdc.com/blog.

4 thoughts on “#VSIT Can I include Visual Studio Integration Toolkit with my installer?

  1. Hi David,

    My name is Justin, and I’m also working with K-ecommerce on the integration of the VSIT for GP 2016 for our software. Yesterday I reached out to Mekorma and spoke with a Sales representative there about the registration process with your toolkit and GP 2016. I understand the process is part of their distribution requirements, however some of the information here in your post I’m not sure matches what I was told by the sales rep. yesterday. Could you help clarify some of this for me?

    I was told that our customers would not have to register, as they are not using the toolkit to create or develop anything themselves. We use the toolkit for our own integration purposes between our software and Great Plains, which we distribute to our customers for their own use. From speaking with Mekorma, we would be considered a “partner” of theirs in this case as we use VSIT in our software, however, as our customers are not using any form of software from Mekorma (solely distributed or otherwise), they would not have to go through any registration process themselves with Mekorma.

    To summarize, they are not using the toolkit themselves, but they are using our software that was built with the toolkit for integration with GP in mind. Our customers are essentially end users of GP, using what would be in this case a built-in extension for credit cards.

    Does this make sense from what I was told, or am I misunderstanding or missing something?


    • Hi Justin

      Please don’t think of the toolkit as an object packaged with your solution like a .Net object you can purchase. It is a toolkit that once installed on a system can be used by any Visual Studio Tools developer to add menus for multiple addon customisations.

      The registration system is tied into the Dynamics GP registration information of the current system and so does require registration for each customer site.

      Please note that this change in VSIT is not just for GP 2016, but for all current versions of GP.



Please post feedback or comments

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

WordPress.com Logo

You are commenting using your WordPress.com 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

This site uses Akismet to reduce spam. Learn how your comment data is processed.