If you have not read the previous article on Future Proof range setting, check it out below:
When I train people on Dexterity I show them a better method to set indexed ranges than the style you will often see in older code or by developers who have not yet been “converted”.
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 was recently assisting a fellow Dexterity developer to create scripts to automatically create all the Security Tasks and Security Roles for their ISV (Independent Software Vendor) add-on product for Microsoft Dynamics GP.
While they were checking their code in Dexterity Test mode, the security settings for their product never showed up. This was weird as the data appeared to be in the tables and worked when in Runtime mode.
In this article, I will take you through the errors you could get and how to resolve them. Some of these you might know from previous versions, others are new to 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.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Last week, I had an interesting case where a Dexterity Developer was having trouble getting some code to update a range of records selected in a table. The code would only update the first record in the range.