I wanted to take an opportunity to respond to the feedback with some history and facts about the product that will explain why it now requires registration.
For the Visual Studio Tools for Microsoft Dynamics GP developers out there, I am pleased to announce that the next build of the Visual Studio Integration Toolkit for Microsoft Dynamics GP (VSIT) is now available for download.
The Visual Studio Integration Toolkit was previously known as Menus for Visual Studio Tools (MVST), which was discontinued in October 2014. If you are still using the previous product, please upgrade to the supported product.
The Batch Posting Service Toolkit provides service procedures to retrieve a list of Batch Numbers for a specified Batch Source and to post the batch for a specified Batch Source and Batch Number.
It is designed to be used to post newly integrated batches of transactions real time and can be called via Dexterity, Visual Studio Tools or as a Service Based Architecture (SBA) Web Service (for v14.0 or later).
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.
Have you ever written some cool Visual Studio Tools (VST) code that worked great on the desktop client, but does not work on the web client? VST code that does not use any WinForms or uses WinForms but only with supported controls and so should work?
Well, I have. A great example is the Company Login window customisations covered in the blog posts below:
- Customising the Company Login window series – Visual Studio Tools revisited – Visual C#
- Customising the Company Login window series – Visual Studio Tools revisited – Visual Basic .Net
The code worked fine on the desktop client, but had no effect in the web client. Something was missing, but I did not know what.
Following on from my last post, Customising the Company Login window series – Visual Studio Tools revisited – Visual C#, where I completed the Customising the Company Login window customisation using Visual Studio and Visual C#, I wanted to create the same example using Visual Basic .Net.
Thanks to Tim Wappat from the Dynamic Coding Blocks blog for his post which helped me get past the issues I was having accessing the Continuum Integration Library:
Just before I left Microsoft, I was writing a series of blog articles about Customising the Company Login window so that you could see the full company name in the drop down list for long company names.
I had shown how to achieve the customisation with Dexterity and with Visual Basic for Applications, but was having problems getting it to work from Visual Studio Tools.