#VSIT Visual Studio Integration Toolkit replaces Menus for Visual Studio Tools

David Meego - Click for blog homepageGreat news for Visual Studio developers.

Winthrop Development Consultants are pleased to announce the release of the Visual Studio Integration Toolkit for Microsoft Dynamics GP (VSIT).

The Visual Studio Integration Toolkit replaces Menus for Visual Studio Tools and is now available for Microsoft Dynamics GP 2010, Microsoft Dynamics GP 2013 (including GP 2013 R2) and also for Microsoft Dynamics GP 2015.

The new name is to reflect the change of ownership as well as the future of the tool where its functionality will be extended to provide access to other “Dexterity only” integration features and not just the current menu navigation.

However, to maintain compatibility with existing installations and projects, the file and object names have not been changed.

The new product releases replace the existing code for GP 2010 and GP 2013 as well as adding the long awaited version for Microsoft Dynamics GP 2015.

Note: The original code for Microsoft Dynamics GP 10.0 is also available, if needed.

Thank you for your patience as the agreement with Microsoft was reached and then the updated code and documentation was developed.

Important: When installing the new code on a system which already has the existing code, you will be asked to restart Microsoft Dynamics GP to complete the renaming of the product. You will also need to remove and re-add your reference to the Application.MenusForVisualStudioTools.dll assembly in your Visual Studio projects.

For more information please see the Visual Studio Integration Toolkit Portal page:

More information on the additional functionality being added to the registered version will be posted on this blog, so watch this space.

Please post comments and feedback.


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

22 thoughts on “#VSIT Visual Studio Integration Toolkit replaces Menus for Visual Studio Tools

  1. The code is finally freed! Congrats on getting everything worked out with Microsoft. I’m very happy that your bazillion hours you’ve spent on this and TWMBSSDGPPPSATPLCPAT4MSDGP is going to turn into a new product.


  2. Hi ,
    GP2015 gets crashed
    In the addins folder i kept Application.Dynamics,Microsoft.Dexterity.Bridge ,Microsoft.Dexterity.Shell, Application.MenusForVisualStudioTools.dll,Application.MenusForVisualStudioTools.xml
    and the sample dll provided VSTMenusVB.dll
    now GP gets crashed and give error
    Application: Dynamics.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileLoadException Stack: at System.Reflection.RuntimeAssembly._nLoad(System.Reflection.AssemblyName, System.String, System.Security.Policy.Evidence, System.Reflection.RuntimeAssembly, System.Threading.StackCrawlMark ByRef, IntPtr, Boolean, Boolean, Boolean) at System.Reflection.RuntimeAssembly.nLoad(System.Reflection.AssemblyName, System.String, System.Security.Policy.Evidence, System.Reflection.RuntimeAssembly, System.Threading.StackCrawlMark ByRef, IntPtr, Boolean, Boolean, Boolean) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(System.Reflection.AssemblyName, System.Security.Policy.Evidence, System.Reflection.RuntimeAssembly, System.Threading.StackCrawlMark ByRef, IntPtr, Boolean, Boolean, Boolean) at System.Reflection.RuntimeAssembly.InternalLoadFrom(System.String, System.Security.Policy.Evidence, Byte[], System.Configuration.Assemblies.AssemblyHashAlgorithm, Boolean, Boolean, System.Threading.StackCrawlMark ByRef) at System.Reflection.Assembly.LoadFrom(System.String) at Microsoft.Dexterity.Bridge.AddinManager.LoadAddinsFromFolder(System.String, Int32) at Microsoft.Dexterity.Bridge.AddinManager.InitializeAllAddIns() at .InitAddIns() at ._WinMainCRTStartup()


  3. Hi Gaurav

    The following DLLs are already in the application folder and should not be in the addins folder. In the Visual Studio project the copy local property of the reference should be false.

    Application.Dynamics,Microsoft.Dexterity.Bridge ,Microsoft.Dexterity.Shell,

    The VSTMenus.cnk/dic and Application.MenusForVisualStudioTools.dll should also be in the application folder.

    The Application.MenusForVisualStudioTools.xml file does not need to be deployed, It is only needed for development to provide IntelliSense.

    Only the VSTMenusVB.dll file should be in the Addins folder.

    Loading the same DLLs multiple times is probably the cause of your errors.



  4. Hi Antony.

    Is your issue related to the Visual Studio Integration Toolkit, which is the topic of this article?

    I am still not sure what your issue is.

    The picture and native picture resources for Dynamics GP are contained in the DYNAMICS.DIC dictionary file.



  5. Hi David, Please let me know if are going to release the Visual studio integration toolkit for GP2016 and above version


    • Hi David,

      Can you please suggest anything about this one

      I would like to register a trigger in before closing event (if any exists) dynamics GP from Exit button or from the direct close(X) from top of GP.

      Public Class GPAddIn

      Implements IDexterityAddIn

      ‘ IDexterityAddIn interface

      Sub Initialize() Implements IDexterityAddIn.Initialize

      Please suggest something which I register here and that event called before closing the GP,the event registere would check the resourses(e.g. Connection) if already opened then need to close

      ‘AddHandler Dynamics.Forms.Toolbar.MainMenu1.CloseBeforeOriginal, CloseOpenResources()

      Any help Please!!!!.

      Regards Gauji Jo BatchMaster Software, Inc.


      • Hi Gauji

        Please note that blog comments are not an appropriate platform for support. You should really post questions like this on the public forums, so others can answer and/or benefit from the answers.

        Anyhow, I would look at either the toolbar form close event or the main menu form close event.



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