Visual Studio Integration Toolkit Portal

This is the portal page for Visual Studio Integration Toolkit for Microsoft Dynamics GP (based on the product previously known as Menus for Visual Studio Tools for Microsoft Dynamics GP).

Find this page using the URL:

Below are the current release details:

  • For Microsoft Dynamics GP (v18.2) Modern Lifecycle:
    Build 15.8 (Last Modified: 15-Feb-2020), Installer: 18.02.0015.8
  • For Microsoft Dynamics GP 2018 & GP 2018 R2 (v18.0):
    Build 15.8 (Last Modified: 15-Feb-2020), Installer: 18.00.0015.8
  • For Microsoft Dynamics GP 2016 & GP 2016 R2 (v16.0):
    Build 15.8 (Last Modified: 15-Feb-2020), Installer: 16.00.0015.8
  • For Microsoft Dynamics GP 2015 & GP 2015 R2 (v14.0):
    Build 15.8 (Last Modified: 15-Feb-2020), Installer: 14.00.0015.8
  • For Microsoft Dynamics GP 2013 & GP 2013 R2 (v12.0):
    Build 15.8 (Last Modified: 15-Feb-2020), Installer: 12.00.0015.8

Below are the no longer developed release details:

  • For Microsoft Dynamics GP 2010 (v11.0):
    Build 15.7 (Last Modified: 30-Sep-2019), Installer: 11.00.0015.7


Visual Studio Integration Toolkit for Microsoft Dynamics GP is a Dexterity integrated software tool which contains an Application Programming Interface (API) that can be called from Visual Studio development system using Visual Basic or Visual C# development languages to integrate with functionality normally only available in Microsoft Dynamics GP via the Dexterity development environment, such as menu navigation amd area pages. Build 15 adds a suite of helper functions.

It contains a Dexterity Chunk and an associated assembly for use with Visual Studio Tools. Also included is full documentation and examples showing how to implement the code for both C# and VB.Net.

Release Announcements

Below are the links for the various release announcement blog posts:

Frequently Asked Questions

These links provide additional information about the Visual Studio Integration Toolkit:


IMPORTANT NOTICE: To ensure continued registration and the best experience, always install the latest build. Install over the top of the existing build, no need to uninstall first. You can also copy the updated files from one install to other installs.  See article: Updating Visual Studio Integration Toolkit.

The download links and User Guide Manual Documentation are available from the following page:

Note: The manual is included with the installer, but is also available as a separate download.

Support Information

Support for Visual Studio Integration Toolkit is provided by Winthrop Development Consultants.

Support cases can be logged using the Contact Support page:

Ordering Information

For customers, the standard functionality of the Visual Studio Integration Toolkit is offered free of charge, but does require registration (renewed automatically each year). This is David Musgrave’s gift to the Microsoft Dynamics GP Community.

Partners can register their customers for automatic registration (see below) or customers can register manually.

For manual registration, just fill in the Contact Details from the Registration Window (Help >> About Microsoft Dynamics GP >> Additional menu >> About Visual Studio Integration >> Registration) and a free annual subscription will be automatically generated.

Any ordering questions can be sent via the Contact Sales page:

Partners can request permanent Not for Resale (NFR) registration keys.

Please sign up as a partner with Winthrop Development Consultants on the Partners page and you are automatically entitled to NFR registration keys for your in-house or demonstration systems.

Or, for immediate access, you can enter your partner Contact Details manually and request to be converted to partner status later.

Note: Partners must be using registration keys with their registered site name and not demo keys with Two, Inc. for NFR registration to work.

Partners can register customers by providing the same details as above to have their customers automatically registered and for the customer to be associated with the partner company.

If you need immediate access, you can also register the customer’s Contact Details manually and then request the customer be associated to your partner company later.

More Information

For more information, please see the Visual Studio Integration Toolkit pages on the Winthrop Development Consultants site:

Other Articles and Posts

For other related articles and posts have a look at the Visual Studio Integration Toolkit category page.

Comments and Feedback

Please provide comments, feedback and suggestions for the Visual Studio Integration Toolkit to help us understand how we can improve it.

Last Updated: 19-May-2020.

22 thoughts on “Visual Studio Integration Toolkit Portal

  1. Why would the VSTM_1400 package generate a trusted application issue in an addin for GP 2015?

    An exception occurred while trying to load or initialize the addin located at D:\SQL\PROJ\GP2015\GP2015\Addins\ProjAddIn.dll. Exception Details: System.Security.SecurityException: That assembly does not allow partially trusted callers. at Microsoft.Dexterity.Applications.MenusForVisualStudioToolsDictionary.VstmCommandFormForm..ctor() at Microsoft.Dexterity.Applications.MenusForVisualStudioToolsDictionary.VstmCommandFormForm.get_Instance() at Microsoft.Dexterity.Applications.MenusForVisualStudioTools.MenusForVisualStudioToolsForms.get_VstmCommandForm() at ProjAddIn.GPAddIn.Initialize() in d:\Projects\VS2013\PROJ\GP Addins\GP2015\ProjAddIn\ProjAddIn\GpAddIn.cs:line 23 at Microsoft.Dexterity.Bridge.AddinManager.LoadAddin(String name, Type type, Boolean checkPlatformAttribute, Int32 currentDexPlatform) The action that failed was: LinkDemand The assembly or AppDomain that failed was: Application.MenusForVisualStudioTools, Version=, Culture=neutral, PublicKeyToken=8e4d244f870d4c63 The method that caused the failure was: Microsoft.Dexterity.Bridge.NamedCollection`1[Microsoft.Dexterity.Bridge.DictionaryForm] get_Forms() The Zone of the assembly that failed was: Internet The Url of the assembly that failed was: file:///D:/SQL/Proj/GP2015/GP2015/Application.MenusForVisualStudioTools.DLL


  2. Solution for that last comment — I found the physical file had a block on it when it was copied from your site to my computer. Unblocking the file did the trick


  3. Hi Devesh

    Did you follow the link in the downloads section above. Downloads are available for GP 2010, 2013, 2015 and 2016.

    Please note that registration is required, but there is no charge.



  4. Hey David,

    With Menus for Visual Studio Tools, I could just include the chunk file and dll in my AddIn installation package so users only had to install a single package. Is this no longer an option and users will need to install Visual Studio Integration Toolkit separate from my add-ins?




    • Hi Derek

      You will need to install Visual Studio Integration Toolkit as it needs to write some registration entries as well. It also has additional files now.

      Sorry for the extra step, but that is how it works now.



    • Hi Derek

      Just thinking…. the VSIT installer supports silent install and so you could install without showing it.

      Also, if you pre register the customer’s details with Mekorma, the keys will be automatically installed and the customer will never see the registration.



  5. Hello David,

    This message is from K-ecommerce(Owner of Azox company)
    We have a package to add some custom menus in GP and we use the Menus for Visual Studio Tools for several years.
    For GP2015 and previous versions, it works well by installing our package with chunk files and dlls. GP users don’t need to install or register the product.
    For this version GP2016, they have this error message: “Visual Studio integration Toolkit is not registered” and when they click on Yes to register the product, GP shows the about window . Here if they click on registration button, GP asks for another product that needs to be installed.

    • Is there a version of Menus for Visual Studio Tools for GP2016 that works without request a registration in each user installation(billable or not)?
    • All users need to install the Visual Studio Integration Toolkit and register its GP company?

    In development mode
    • Where do we need to register it? Is there a way without going in GP to do so? Like when building it with a package? Usually it creates the dll and chunk file directly in Gp, but there doesn’t seem to be a place where you can register the dll.

    Thanks for your answers


    • Hi Wilbert

      Menus for Visual Studio Tools was discontinued when I left Microsoft in October 2014. I was able to get the rights to it and re-release it as a Winthrop Product.

      I needed a way to track usage of the product and do plan to add additional functionality which will be charged as an optional module. The registration (and installer) is now part of all current versions GP 2010, 2013, 2015 and 2016.

      The registration is per customer site and free of charge for the core functionality. You just need to contact to get the customer registered (need the site name and account number).

      If the registration has been organised with Mekorma, the keys will be retrieved automatically via a web service and the user will not need to enter them. So just organise them before you install and the user will not see anything.

      You can also do a silent install with the installer executable, so that you can distribute without needing extra steps for the user to see.

      You will need the code installed on all workstations.

      For your development systems, you can contact and request NFR (Not for Sale) registration for your site name and account number. Also, no keys are needed for the Fabrikam sample company.

      Hopefully, this answers all your questions.



  6. Thanks for your answer,
    Currently, we are partners and we have a product that uses VSIT. We have customers that will use our product in GP2016

    My questions:
    When you said: The registration is per customer site and free of charge for the core functionality. You just need to contact to get the customer registered (need the site name and account number).

    That’s mean that it’s not necessary for our customers to go through this page We just need to send an email to with customers’ site name and Microsoft account number right? Or it’s mandatory for each one of our customers places an order through the order page to get the registration.

    Note: Even if this product is free of charge, the order page require payment information.



  7. Hi Wilbert

    The customer needs to be registered, there is no problem with you organising that on their behalf.

    Note: the credit card information on the order page only allows you to confirm you wish to use a particular credit card, the details for which have already been provided to Mekorma. You should be able to leave it blank or say you will pay via cheque (which will not be required).

    If you have any further questions on organising the registration, just email



  8. Hi,

    I recently added Visual Studio Integration Toolkit to GP on an onpremise server on a GP that is registered with Mekorma, but I keep getting the error code -17 when I load GP. I know the error is caused by the registration not being there, but it’s there. Afterward, if I close GP and open it back, it work correctly. Trying to reproduce the error again, by closing it back and forth do not always trigger the error.

    We have your product on other server for different client, and this is the first that caused this error randomly.

    Not sure if related but :
    If I go to Mekorma Products Registration and try to close the window via the X, it say :

    An open operation on table “ME_CfgStubs_MSTR” failed accessing SQL data.

    With more info :

    [Microsoft][SQL Server Native Client 11.0][SQL Server]Database ‘LIVE1’ does not exist.

    Also it’s for GP2016.

    Thank you !


    • Hi Maxim

      Blog comments are not the best platform for support, please contact

      You might try making sure that the Visual Studio Integration Toolkit product appears above the Mekorma Product Manager in the Dynamics.set. If you have GP Power Tools, use the Dictionary Control window to move the products around.



    • If you are doing Silverlight development for the GP 2015 Web Client and still have the ability to trigger events on and call to Dexterity functions and procedures it should still work. I have never tried it, so let me know how you go.



      • Thanks for your time David.

        I am developing some SSRS reports and need to call from forms developed using VSTools. I need call this windows using the menu.
        Form contain datepicker control and default rendering is not working for this control. So I want do the silverlight development. Any alternative is there to call Sliverlight forms from GP interface



      • Hi Raj

        I have never worked with Silverlight and so cannot provide any more information.

        As long as you can open your WinForm, VSIT is doing its job.



  9. Hi David! I recently installed the VS Integration Toolkit on a Dynamics GP 2013 test system I’m building. Everything seemed to be working fine until I went through the registration process. The registration key appeared to download and be applied appropriately, however, the next time I launched GP (and now subsequent times too) I’m getting the following error message…

    An error occurred while loading or initializing an addin. Ask your administrator to check the Windows event log for more details. Dynamics will now close.

    And this is the error I’m receiving in the Application event log…

    An exception occurred while trying to load or initialize the addin located at C:\Program Files (x86)\Microsoft Dynamics\GP2013\Addins\WinthropDC.VisualStudioIntegrationToolkit.dll. Exception Details: System.IO.FileNotFoundException: Could not load file or assembly ‘Application.MenusForVisualStudioTools, Version=, Culture=neutral, PublicKeyToken=8e4d244f870d4c63’ or one of its dependencies. The system cannot find the file specified. File name: ‘Application.MenusForVisualStudioTools, Version=, Culture=neutral, PublicKeyToken=8e4d244f870d4c63’ at WinthropDC.VisualStudioIntegrationToolkit.GPAddIn.Initialize() at Microsoft.Dexterity.Bridge.AddinManager.LoadAddin(String name, Type type, Boolean checkPlatformAttribute, Int32 currentDexPlatform) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

    Do you have a suggestion on how to remedy this?

    Thank you!


Please post feedback or comments

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

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