Microsoft Dynamics GP Addin Templates For Visual Studio 2017 & 2019

Posted on November 27, 2019 by Vaidhy Mohan

Tim Wappat has given us something precious. I am late to the party, though.

I didn’t realise that Microsoft Dynamics GP 2018 R2 shipped with a VS Tools version that’s incompatible with anything above Visual Studio 2015.

This realisation hit me when I tried to install and configure GP 2018 R2 on my virtual machine for an upgrade project.

Obviously, the first place to search for a resolution was our GP forum. This post by Richard Wheeler pointed me to the right direction. Tim’s Visual Studio extension saved me from going insane.

Thank you so much, Tim!

Vaidy

GP2016 DAG Issue

Posted on April 28, 2017 by Vaidhy Mohan

I am wondering whether someone has already faced this issue and has shared his/her knowledge on this.

My issue is with GP2016 VS Tools Dictionary Assembly Generator (DAG), where it takes more than 10 mins to complete generating DYNAMICS.DIC assemblies. Not only that, it also doesn’t generate Application.MicrosoftDynamicsGp.dll in the first attempt itself.

Look at the following screenshot:

Screen Shot 2017-04-28 at 01.29.38 pm.png

First two “successful” attempts of running DAG created only the metadata files and not the actual DLL. I’m running the DAG for the third time, as I write this post.

UPDATE: Third time’s the charm. I am baffled, though.

I have no clue, whatsoever, about why this is happening.

My question(s) to all you guys:

Have you faced this issue?
If so, what did you do to resolve it?
If you have not found any solution (other than running DAG till it creates the DLL), have you already reported this to GP dev team?

Please shed some light on this by sharing your thoughts on the comments section.

Vaidy

Quick Tip: Debugging Visual Studio Tools – Developing For Dynamics GP

Posted on July 30, 2013 by Vaidhy Mohan

Awesome tip up there on Developing For Dynamics GP blog on how to debug VS Tools For Dynamics GP.

I am late in blogging about this post. But NOW is the time, as this post just saved my 1/2 day. Seriously. Not kidding. I was stuck with one SQL query execution. There were records to be retrieved, but my code didn’t. After 5-10mins of frustrated troubleshooting, I remembered this post. I should have done that immediately then, but I didn’t.

I setup my VS Tools project to launch GP as instructed on this post and within 2 minutes I could find the issue.

This one deserves to be there on Microsoft Dynamics GP Cookbook (technical).

VAIDY

Caps Lock Reminder – For Microsoft Dynamics GP 2013

Posted on February 26, 2013 by Vaidhy Mohan

I had developed a small customisation module which would alert users while logging on to Dynamics GP with CapsLock key on. You can read more about it here: GP Login Form – Caps Lock Reminder Update.

That customisation was developed using Modifier with VBA. But with Dynamics GP 2013, much emphasis has been given to the new Web Client. Which means, all our VBA code logic won’t be supported by web client.

That said, I have now converted my code from VBA to VS Tools (using C#.Net as programming language). Those who are interested can download it FOR FREE from following link:

CapsLockMessage-12.0.0.1.dll

Instructions to use:

Copy this DLL file and paste it on to GP AddIns folder (can be located inside GP 2013 application folder).
Ask users to log out and log on back.
If you do not need this tool anymore, just remove this DLL from AddIns folder, after all users log out.
This can be used safely in production environment. This tool doesn’t interfere in any of your day-to-day transactional activities. The scope of this is restricted only to GP login form.

Your feedback is always welcome.

VAIDY

Visual Studio Tools for Dynamics GP – A Weird Flaw/Limitation

Posted on February 21, 2013 by Vaidhy Mohan

I must first admit that I faced this issue (or may be flaw…!?!?!?!) only now after all these years of VS Tools development expertise.

The issue is this: I want to write a custom code on two events; SOP Entry Print Button and POP Entry Print Button. When I initialise the event method for SOP Entry Print Button, following is how it generates the code:

And the event method gets created as follows (if you use TAB to create the methods automatically):

After above, when I try to initialise an event method for POP Entry Print Button, following is how it generates the code:

When you try to press TAB to create the event method automatically, it takes you to previously created method.

Because, print buttons on both windows (SOP Entry & PO Entry) have same name technically, which is WindowPrint, VS Tools doesn’t understand both are from different windows and it just goes on to refer to one single method instead of two.

But you are not stuck there forever. Simple solution is to manually name your method initialisation with logical names, like below: