It has been an exciting ride combing through the features and capabilities of the Microsoft Dynamics GP 2015 Service Based Architecture components, starting at the core with the new and enhanced .NET interoperability capabilities within Microsoft Dexterity, all the way to the new service base architecture foundation built into Microsoft Dynamics GP to expand the realm of integrations that can be accomplished in today’s fast paced, application (Apps) dominated world, whether those applications are native to the Windows platform or cross-platform, whether they reside in the cloud or on premise, and regardless of the form factor. I wanted to provide this single point of reference to reach all entries in the series, which saw 5 articles over the past 5 months. Microsoft Dynamics GP 2015 Developer’s Preview: Loading the VHD image – Part 1 (Aug 29, 2014) Microsoft Dynamics GP 2015 Developer’s Preview: Working with Sample URIs – Part 2 (Sep 24, 2014) Microsoft Dynamics GP 2015 Developer’s Preview: .NET Framework Interoperability – Part 3 (Oct 29, 2014) Microsoft Dynamics GP 2015 Developer’s Preview: Dexterity Service Patterns – Part 4 (Nov 25, 2014) Microsoft Dynamics GP 2015 Developer’s Preview: Dexterity Service Patterns – Part 5 (Dec 1, 2014) Since Microsoft Dynamics GP 2015 is now available to the general public, my focus will turn to keeping you abreast of those application nuggets, point out any glaring issues or problems, and continue to work with the development community at large to maximize the technological foundations of the product.
This week saw the release of Microsoft Dynamics GP 2015, six months after the release of Microsoft Dynamics GP 2013 R2. Dynamics GP 2015 introduces over 120 new features, all of which have been covered recently over at Inside Microsoft Dynamics GP , the official blog of the Microsoft Dynamics GP Product Management & Marketing teams. This new release also introduces a first round of Service Based Architecture operations, geared toward enhancing the product integration capabilities, and the ability for developers to expand into areas such as mobile applications, cross-platform applications, cloud-based applications and services, among others.
In my previous article (see Microsoft Dynamics GP 2015 Developer’s Preview: Dexterity Service Patterns – Part 4 ), we discussed the merits of the Wrapped Window pattern and how it can save time by avoiding refactoring of complex business logic embedded on Dexterity forms. I also provided an intro on the Decoupled Logic pattern and why this is the preferred method for exposing Dexterity services as it provides the best performance. However, we also came to the conclusion that refactoring is only feasible in cases where decoupling the business logic from the UI will yield a reasonably increase in performance, without negatively impacting development and product release timelines
What a week of learning that reIMAGINE 2014 conference was! If you stayed for the post conference training classes, even more power to you. In my previous article (see Microsoft Dynamics GP 2015 Developer’s Preview: .NET Framework Interoperability – Part 3 ), I talked about the .NET interop capabilities introduced in this iteration of Dexterity and how these new capabilities have become the foundation for unlimited extensibility options for Dexterity-based applications. Today, I wanted to talk about another aspect brought by .NET interop: Dexterity services. However, to understand Dexterity services, we must first take a look at the service implementation patterns
November 10, 2014 After my pleasant trip to Fargo on the previous day , it was time to check in and complete the registration process with the lovely ladies from Dynamic Communities . It helps to have a reputation in the community as my badge was handed to me without showing an ID
Friday, October 17, 2014 Ok, what just happened last night, ugh! Day 2 was quite the day (and the night!). However, the Summit was coming to an end and it was almost time to close the curtains on what I personally reckon to be a very successful event. This meant participating in the last networking huddle event, which had tables organized by roles; visit the Expo one last time to say bye to ISVs who tirelessly worked to bring some of the best products to market; and attend maybe a session or two going throughout the day