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: http://winthropdc.com/VSIT

Below are the current release details:

  • For Microsoft Dynamics GP 2016 (v16.0):
    Build 11 (Last Modified: 24-Oct-2016), Installer: 16.00.0011.5
  • For Microsoft Dynamics GP 2015 & R2 (v14.0):
    Build 11 (Last Modified: 24-Oct-2016), Installer: 14.00.0011.5
  • For Microsoft Dynamics GP 2013 & R2 (v12.0):
    Build 11 (Last Modified: 24-Oct-2016), Installer: 12.00.0011.5
  • For Microsoft Dynamics GP 2010 (v11.0):
    Build 11 (Last Modified: 24-Oct-2016), Installer: 11.00.0011.5

Overview

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.

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:

Downloads

The download links are at the bottom of Mekorma’s Visual Studio Integration Toolkit page.

Visual Studio Integration Toolkit for Microsoft Dynamics GP – User Guide Manual Documentation

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’ distribution and support partner, Mekorma.

Support cases can be logged using the link below:

Support hours are 6:00am to 5:00pm (US Pacific Time), Monday to Friday.

Pricing Information

The standard functionality of the Visual Studio Integration Toolkit is offered free of charge, but does require registration.

Please place your orders via Mekorma’s Order Now page:

Partners can request Not for Resale (NFR) registration keys. Please email sales@Mekorma.com with the following details:

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

More Information

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

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: 25-Oct-2016

14 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=14.0.0.0, 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

    Like

  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

    Like

  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.

    David

    Like

  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?

    Thanks.

    Derek

    Like

    • 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.

      David

      Like

    • 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.

      David

      Like

  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.

    Questions:
    • 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
    Wilbert

    Like

    • 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 sales@mekorma.com 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 sales@mekorma.com 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.

      David

      Like

  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 sales@mekorma.com 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 http://www.mekorma.com/order/order-now.aspx. We just need to send an email to sales@mekorma.com 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.

    Thanks,
    Cordially

    Like

  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 sales@mekorma.com.

    David

    Like

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 )

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s