The Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.
The tenth Feature of the Day is .NET Interop. The new Service Based Architecture enables Microsoft Dynamics GP and ISV products to expose and consume services. Services are the backbone of the cloud and this feature supports new and exciting scenarios around cloud based interaction.
Developers can now directly reference .NET assemblies and their objects in sanScript in order to leverage capability offered in the .NET Framework. This includes the ability to call out to services or use objects as a means of data handling and processing.
.NET objects can be instantiated, have their properties set or methods called within sanScript
The roles targeted by this feature are:
I started reviewing Leslie Vail’s book, Developing Microsoft Dynamics GP Business Applications, which was published at the end of December by Packt Publishing, a few weeks ago. To do this review I decided to take a read through and complete all the examples she gives on developing an application as I’ve only had very limited experience with Dexterity;
Today, it is time for part 5 of my review where I look at Chapter 6: Deploying a Dexterity Solution where Leslie covers the following key topics:
- System requirements
- Versions and builds
- Table creation routines
- Completing the application
- Creating the chunk file
- Testing in a multi-dictionary environment
- Distributing the completed application
This chapter has a fair bit of explanatory text covering each of the key topics.
I started reviewing Leslie Vail’s book, Developing Microsoft Dynamics GP Business Applications,which was published at the end of December by Packt Publishing, a few weeks ago. To do this review I decided to take a read through and complete all the examples she gives on developing an application as I’ve only had very limited experience with Dexterity;
Today I’m taking a look at Chapter 5 which covers sanScript and how to add it to windows to enable the required functionality. The key topics to be covered are:
- Introduction to sanScript
- Scrolling Windows
After slacking off a lot in terms of reviewing Leslie Vail’s book Developing Microsoft Dynamics GP Business Applications, which was published at the end of December by Packt Publishing, I’m going to try to get a regular tempo of review posts going. Today I’m here with the review for chapter 4;
This chapter is all about Building the User Interface which Leslie does by getting the reader to build an interface for customer contacts integration and covers:
- Creating base resources
- Creating tables and keys
- Creating forms and windows
- Creating scrolling windows
- Working with window fields
- Completing your windows
So from this chapter I expect to get a good grounding in creating an entirely new window which should look like this:
Things have been very hectic recently and I’ve found myself slacking off from reviewing Leslie’s book Developing Microsoft Dynamics GP Business Applications which was published at the end of December by Packt Publishing;
Well, I now have a bit more time so I’ve returned to the book to take a look at chapter 3, Getting Started with Dexterity which gives a thorough look at Dexterity; how to install it’s development environment, what the components are and how they hang together and the pitfalls to watch out for.
I’ve recently started taking a look at Leslie Vail’s book, Developing Business Applications for Microsoft Dynamics GP which was published in December by Packt Publishing. The book was written using Microsoft Dynamics GP 2010; this is not a criticism as the book will have taken a fair time to write and was published two days after Microsoft Dynamics GP 2013 was released so there wasn’t time to do an update to the latest version.
However, Microsoft Dynamics GP 2013 was available I’ve decided to perform the practical examples using this version rather than GP 2010 because I had just finished building a customisation environment with GP 2013 installed in it and I could easily add Dexterity and the other tools used in the book to the environment.
As I was following the steps in Chapter 3 of the book, which is an introduction to Dexterity, where common errors and issues encountered in Microsoft Dynamics GP 2010 and how to resolve them are explained, I came across an error which was specific to Microsoft Dynamics GP 2013;
AZCProject.dic – Could not load file or assembly. ‘Microsoft.Dynamics.GP.BusinessIntelligence.Homepage’ or one of its dependencies. The system cannot find the file specified