1. Locate the current VST templates folders under your Microsoft Visual Studio 2012 program files folder. These can usually be found as follows:
Visual C# templates folders
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\ProjectTemplates\CSharp\Dynamics GP
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\ItemTemplates\CSharp\1033
*The latter folder contains the zip file items associated with the project's Add | New Item.. action in Visual Studio, giving access to Microsoft Dynamics GP Form and Microsoft Dynamics GP Silverlight Window.
Visual Basic templates folders
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\ProjectTemplates\VisualBasic\Dynamics GP
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\ItemTemplates\VisualBasic\1033
*The latter folder contains the zip file items associated with the project's Add | New Item.. action in Visual Studio, giving access to Microsoft Dynamics GP Form and Microsoft Dynamics GP Silverlight Window.
2. Copy and paste the Dynamics GP folder from under the above folders to their corresponding Microsoft Visual Studio 2013 program files folder. These are consequently found at:
Visual C# templates folder
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\ProjectTemplates\CSharp
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\ItemTemplates\CSharp\1033
Visual Basic templates folder
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\ProjectTemplates\VisualBasic
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\ItemTemplates\VisualBasic\1033
3. Configure Microsoft Visual Studio 2013 to recognize the templates. Start a Command Prompt as an administrator and change directories to C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE. Once in the directory, you can type the following command to setup the Visual Studio 2013 environment:
 |
| Command Prompt |
The setup process should take no more than a couple minutes. Once you finish, you can launch Visual Studio 2013 and click to create a project using the Dynamics GP templates installed.
 |
| Visual Studio 2013 with Dynamics GP templates |
Until next post!
MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/
Comments
I have one doubt. Now, I am upgrading the VST project from lower version to GP 2013. So I have used GPconnNet.dll in the old version. So I have removed that dll and added new dll from location C:\Program Files\Common Files\microsoft shared\Dexterity\v2.0. I have build the VST customization and insert into adding folder. The problem is when I am opening the GP it get crashed. I have analysed and found that issue is because of the new dll, it is 64 bit dll. I am confusing here, GP is 32 bit application, then why the 64 bit dll present in that mentioned location. and what is the dll GpConn.dll refers to. Please help me if anybody knows
Regardless of whether GP is a 32-bit application or not, you should be using the GPConnNet.dll as a reference in your project.
Any Event Viewer messages after the crash?
MG.-
Thanks for the great writeup!
I finally installed VS 2013 and am glad to see that there is an option to develop VST for GP solutions with it.
Steve
The same procedures apply to VS2014 as well. You still have to install VST so you can get the DAG tool.
MG.-
I am new in GP.Doing some customization works using in Gp10.0 using visual studio sdk tools 2008.
I tried to deploy the modified forms using export and import method, after importing that changes not reflected in the second machine.
May I know the steps to deploy customized forms.
Thanks in advance.
And what about cmd?
No, this does not apply to VS2019. VS2018 forward changed to a manifest base model for adding extensions. Tim Wappat, out of the UK, created the GP extension manifests which can be downloaded from the Visual Studio marketplace.
https://marketplace.visualstudio.com/items?itemName=timdotnet.MicrosoftDynamicsGPItemandProjectTemplates