Following on from my previous posts: Customising the Company Login window series Part 1 – Introduction , Customising the Company Login window series Part 2 – Visual Basic for Applications and Customising the Company Login window series Part 3 – Dexterity , here is a discussion about trying to create a solution using Visual Studio Tools.
After the successes of the All Saints College teams at the RoboCup Junior Australia 2014 WA State Championships , it went without saying that we would take our best teams to the National Competition in Brisbane on the 27 th and 28 th September. We ended up taking our Senior Theatre (Pickle JAR Productions) and Senior Dance (The Inspector) teams as well as our top 2 Open Rescue (Sam and Me, Him & It) teams. Sadly neither of the CJs (Christopher Jack and Christopher John) were able to come due to other commitments
It has been a while since my last post. I have been very busy with a number of activities (more on that in a later post). One of those activities has been this year’s RoboCup Junior Australia competition. For the last two years I have been the mentor for the All Saints College Robotics Club.
A new book by fellow Microsoft Most Valuable Professional Ian Grieve is now out about the Web Client – Implementing the Microsoft Dynamics GP Web Client . I was fortunate enough to review the book as Ian was writing it. Ian has created a great tool to supplement the ton of documentation available from Microsoft
As we move into the world of Service Based Architecture with Dynamics GP 2015, we wanted to highlight some debugging tools that will aid you as you create service procedures of your own. Today you have various things available to you to debug integrations as they are created. Among them are internal tools like the Dexterity script logs and the debugger or methods as simple as dropping the .set file on the runtime executable to ensure Dynamics still launches without error. There are numerous external tools at your fingertips as well such as SQL Profiler, Task Manager and Event Viewer. While you will continue to find great value in these going forward when debugging things “inside” of the Dynamics GP environment we wanted to add tools for gathering information for all of the service events happening “outside” this environment and coming into the Dexterity Process. While considering the options we knew we wanted to create debugging that was low impact on the process overall and incredibly performant. We wanted to not only provide you errors that were encountered within the service but also provide context to enable easier and quicker debugging. Along with this we wanted to provide a sufficient level of logging by default to strike a balance between usefulness and performance. To enable this we decided to utilize Event Tracing for Windows (ETW).
How to Fix a Setup File is from a later version Error from the Support Debugging Tool when doing a Test Upgrade
This post revisits the issue previously discussed in the blog post: How to Fix a Setup File is from a later version Error from the Support Debugging Tool . The issue is that you receive the error message below from the Support Debugging Tool just after logging into Microsoft Dynamics GP: Setup File is from a later version (##.##.####) than the version (##.##.####) of the Support Debugging Tool on this workstation. Please check with your administrator if the correct location for the Debugger.xml setup file is being used