I have been fairly quiet recently on the blog and forums as I have been concentrating on developing the next build of GP Power Tools. All I can say is that it is awesome and you will love it. I have a “Sneak Peak” article coming soon.
While working on the development and testing process, I had some unusual behaviour from my .Net Visual Studio Tools Addins and spent an entire day troubleshooting the issue so I could identify the cause and work out a solution. Read on for the gory details….
This article comes about because we have identified a feature of GP Power Tools that does not work as expected on the Web Client. GP Power Tools has the ability to run scripts and register triggers against Modifier added fields and Modal Dialogs. These features uses the Dynamics.Application object and in particular a suite of functionality historically known as “Continuum”.
We can now confirm that the Dynamics.Application object is not available at all when running Microsoft Dynamics GP in the Web Client and so any functionality reliant on this object will fail to work.
As a follow on to the recent post : #GPPT Why every GP site needs GP Power Tools – Developer Tools, this article explains the benefits of replacing your VBA (Visual Studio for Applications) and VSTools (Visual Studio Tools for Microsoft Dynamics GP) customizations with GP Power Tools.
It has been prompted by the issues seen because the redistributable version of VBA that is packaged with Microsoft Dynamics GP has reached end-of-life as explained in the following article from the Microsoft Dynamics GP Support and Services team:
The release of Build 15 of the free product Visual Studio IntegrationToolkit is a bonus to Visual Studio Tools for Microsoft Dynamics GP developers around the globe.
As well as the enhancements to the Menu Navigation functionality and the addition of support for custom Area Pages, Build 15 adds a new Helper functions module with over 220 functions.
This build is the result of a month’s development effort and is why you have not heard much from me on the blog recently.
I recently had issues with one of my products and need to share the cause of the issue and the solution with the Microsoft Dynamics GP development community.
I made changes to all my products late last year, introducing a new registration system. The code uses Visual Studio Tools for Microsoft Dynamics GP addin DLLs written in Visual C# to handle all the communication with the appropriate registration server.
I am writing this article after seeing the side effects of Visual Studio Tools developers not following Best Practice when adding references to their projects.
Two mistakes made by the developer in this example resulted in Microsoft Dynamics GP failing to launch with the “An exception occurred while trying to load or initialize the addin” error.
I am pleased to announce that the next build of GP Power Tools for Microsoft Dynamics GP (GPPT) is now available for download.
GP Power Tools is the industry leading suite of tools to designed to make your Microsoft Dynamics GP life simpler and easier. Features have been specifically designed and created to enhance the user experience, simplify the administrator experience and provide power debugging and customisation tools to consultants and support engineers.
This is why GP Power Tools should be installed on every workstation of every Microsoft Dynamics GP system globally.
IMPORTANT INFORMATION FOR ALL USERS OF VISUAL STUDIO INTEGRATION TOOLKIT
This article is to announce a new build of the Visual Studio Integration Toolkit for Microsoft Dynamics GP (VSIT) is now available for download.
This new build coincides with the change in ordering and support for Visual Studio Integration Toolkit. From now on, Winthrop Development Consultants is handling all distribution and support for Visual Studio Integration Toolkit directly. Mekorma will no longer be involved with this free product.
Thanks to Kim Peterson from Dynamics Connections, I am pleased to release a new video demonstration of Winthrop Development Consultants’ GP Power Tools (build 23).
Watch to learn why every Microsoft Dynamics GP site globally should have GP Power Tools and why many partners now install GP Power Tools as part of their standard installation.
Hey Developers… Are you attending the GPUG Summit 2017 conference in Nashville, Tennessee in October? If so, this article is to let you know about Microsoft Dynamics GP related Developer content at the conference.
I asked why there was not much content for developers at GPUG Summit and I was told that there are not many developers in attendance. I disagreed and requested a session for Developers, which Bob McAdam promptly organised … thanks Bob. 🙂
From the team that brought you Friday Funny: I Want My MVP.
From the developers of PostMaster…. comes an amazing new customisation tool….
Yes, Andrew Dean from Envisage Software along with Steve Endow MVP from Precipio Services have been busy working away on some really cool technology for Visual Studio Tools developers and have just released it as a free tool.
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.
Great 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.
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:
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.
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.