GP 2015 VS Tools Installation Error


I was trying to install VS Tools for GP2015 R2 on my machine that has already got VS Tools for GP2016 installed. I could not complete the installation and received following error message (and its corresponding Event Log).

Screen Shot 2016-05-13 at 3.16.03 PM

Please note, on the event log, it says “GP 2016 SDK” while I was trying to install GP2015 VS Tools SDK.

Has someone faced this error? If so, could you please share with us on how you resolved it? Have you resolved it at all?

Please lend your inputs on the comments section.

VAIDY

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


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


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:

  1. Copy this DLL file and paste it on to GP AddIns folder (can be located inside GP 2013 application folder).
  2. Ask users to log out and log on back.
  3. If you do not need this tool anymore, just remove this DLL from AddIns folder, after all users log out.
  4. 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


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:

Snip20130221_4

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

Snip20130221_5

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

Snip20130221_6

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:

Snip20130221_7

And like below:

Snip20130221_8

Visual Studio Tools for Dynamics GP does not restrict you from using only names that it suggest.

VAIDY