#Dexterity Development Environments – Part 2: Setting up Projects
This is the second article in my series about setting up your Dexterity Development Environments.
If you have not read the previous article, please do so first using the link below:
Click here to
Subscribe to
our Newsletter
This is the second article in my series about setting up your Dexterity Development Environments.
If you have not read the previous article, please do so first using the link below:
This article has been a long time coming and is the first of a series of articles on how I set up my machine for developing Dexterity applications across multiple versions.
I promised I would detail how my system is set up a while back at the reImagine 2015 conference and had never got around to writing the article until now.
Microsoft Dynamics GP 2015 R2 added lots of new features and enhancements and fixed a number of bugs too. However, it also introduced a change that is now causing errors in some ISV’s (Independent Software Vendor) products.
I first came across this issue when preparing to release GP Power Tools build 22 and was testing the Database Validation feature on my Microsoft Dynamics GP 2016 install.
After months of work, I am extremely excited to announce that GP Power Tools for Microsoft Dynamics GP (GPPT) Build 22 is now available for download. Please update your systems to get all the new features.
GP Power Tools was previously known as Support Debugging Tool (SDT), which was discontinued in October 2014. If you are still using the previous product, please upgrade to the supported and much better GP Power Tools product.
Since forever, the pundits have been preaching the demise of Great Plains Dynamics / Microsoft Dynamics GP.
When I joined Microsoft in 2001, one of the things that influenced my decision was the thinking that Dexterity (the language behind Dynamics GP) was going to die and so I decided that I would be better off inside Microsoft than continue working as an ISV (Independent Software Vendor).
Now sixteen years later in 2017 and I am back working as an ISV, and Dexterity, along with Microsoft Dynamics GP, is still going strong… despite the launch of Dynamics 365.
At the end of last year, Microsoft Dynamics GP 2016 R2 was released.
If you have not already installed/updated to this build, Microsoft has released lots of information about the new features in blogs, documentation and video forms.
I had a nice surprise this morning. I received an email from Terry Heley from the Microsoft Dynamics GP Support team notifying me of the release of Microsoft Dynamics GP 2016 R2.
This should not have been much of a surprise as the release was promised to be at the start of December at the reIMAGINE 2016 conference. I think the surprise was that December is here already. Christmas is getting closer.
This is the sixth in a series of blog posts where I will be highlighting Microsoft Connect product suggestions that need the community’s support. If you agree with the product suggestion, please help get as many votes as you can.
In the last eight years, there have been an increasing number of display issues when using Microsoft Dynamics GP on high resolution monitors. There are a number of different factors coming into play which cause Dynamics GP to display incorrectly.
This article explains the issues, their causes and their solutions and finally explains how GP Power Tools makes the solutions extremely simple to implement.
[Edit] FYI: Build 29 of GP Power Tools automatically applies the fixes during installation. If installing on a Terminal Server, make sure to use Install Mode (see below) so that the settings are rolled out to all users.
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 was previously known as Support Debugging Tool (SDT), which was discontinued in October 2014. If you are still using the previous product, please upgrade to the supported and much better GP Power Tools product.