So I thought it would be worth while mentioning some guidelines to make the install as smooth as possible.
Firstly, let’s discuss the contents of the downloaded archive file. The archive contains the following files:
This is the self-installing dictionary containing the Dexterity code for GP Power Tools.
This is a self-installing dictionary used for migration from the Support Debugging Tool. It is almost identical to GPPTools.cnk but uses the Debugger.* filenames.
This is required when the Debugger.dic file is already installed as extracting a chunk file will not update the launch file if it already exists. So this will overwrite the old dictionary file and then update the launch file to have the new names for the product and files. When Dynamics GP is restarted, everything now points to the new GPPTools.dic and the code removes Debugger.* files.
Only install this file if the Support Debugging Tool is already in the launch file.
This is the read me file which version history information. Installation is optional.
This is the user guide for GP Power Tools. It must be installed if you want the application help system to be able to open the file.
This is the license agreement for GP Power Tools which you accept by using the product. Installation is optional.
This is the signed Dictionary Assembly for the GP Power Tools Dexterity dictionary.
This is the IntelliSense data for Visual Studio for the GP Power Tools Dexterity dictionary.
This is the signed Dictionary Assembly for the GP Power Tools Service Enabled Procedures. For version 14.0 or later.
This is the IntelliSense data for Visual Studio for the GP Power Tools Service Enabled Procedures. For version 14.0 or later.
This addin dll adds Visual C# support to GP Power Tools. Removal will disable the ability to execute Visual C# scripts.
This addin dll adds Visual Basic.Net support to GP Power Tools. Removal will disable the ability to execute Visual Basic.Net scripts and execute Dexterity sanScript against modified dictionaries.
Use the following steps will install GP Power Tools:
- Copy the files to the Microsoft Dynamics GP application folder and the two dlls to the Addins folder.
- For the dll files, right click and select Properties and click the Unblock button if it is shown on the bottom of the first tab.
- Launch Microsoft Dynamics GP using Run as Administrator.
- If asked to restart after launch file changed, go back to step 3.
- Log into Microsoft Dynamics GP using a user ID with system administrator or DBO privileges, such as ‘sa’ or ‘DYNSA’.
- GP Power Tools will create its tables and read in the Debugger.xml file if upgrading from the Support Debugging Tool.
- You will be asked to assign security to all users, recommended to respond Yes.
- You will be reminded to manually assign security to the administrator level users.
Once installed, GP Power Tools can be accessed from the Application and window level Tools menus, the GP Power Tools area page as well as from the GP Power Tools sub menu on the application menus.
Disclaimer: As with all beta code, it is provided “as is” and you use it at your own risk.
If you receive errors from the two Addin dlls, they can be removed to avoid the errors. However the Visual C# and Visual Basic.Net functionality they provide will not be available. Please let me know if you have this issue.
Enjoy the beta and please provide feedback as comments on this post and via the survey built into GP Power Tools.
This article was originally posted on http://www.winthropdc.com/blog.