It’s that time of the year again. While we prepare to celebrate the holidays, be it Christmas, Hanukkah, Milad un Nabi, or simply enjoy a good time off with family and friends, it is also time to begin thinking about 2015. The next major event in sight, of course, is Microsoft Dynamics Convergence 2015 Atlanta and who better to open the event that Microsoft’s newly minted Chief Executive Officer, Satya Nadella .
Following on from my last post, Customising the Company Login window series – Visual Studio Tools revisited – Visual C# , where I completed the Customising the Company Login window customisation using Visual Studio and Visual C#, I wanted to create the same example using Visual Basic .Net. Thanks to Tim Wappat from the Dynamic Coding Blocks blog for his post which helped me get past the issues I was having accessing the Continuum Integration Library: How to make GP company login text boxes longer Using the same approach as the Visual C# example, I repeating the process using Visual Basic .Net. Below are the steps I used for Visual Basic .Net Ensure Visual Studio Tools for Microsoft Dynamics GP is installed
As a fan of Windows Phone I have been enjoying the latest series of adverts where Apple’s Siri is compared to Cortana. Here is a selection of the adverts for your viewing pleasure. Siri vs
As promised, Microsoft has released Dynamics GP 2015 on time! 120+ enhancements were introduced, see below the first look into the product: Before you plan your upgrade, keep in mind that SQL 2008 is no longer supported, you must upgrade at least to SQL 2012 or later. 1
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