Skip to main content

Creating a Microsoft Dynamics GP integration with eConnect and Visual Studio

by Gloria Braunschweig
President, Dorian Enterprises, Computeration, Inc.
July 22 2013

Now that you have successfully installed eConnect, we will examine the process of creating an integration to Microsoft Dynamics GP built with Visual Studio and the eConnect .NET API.  We will build a sample application, then dig into a few key details of the process that can be applied to any integration of this sort. 

The eConnect API consists of two assemblies: Microsoft.Dynamics.GP.eConnect.dll and Microsoft.Dynamics.GP.eConnect.Serialization.dll.  These assemblies can be found in the Program Files (x86)\Microsoft Dynamics\eConnect 12.0\API folder after installation of eConnect.

Each of these assemblies contains a namespace corresponding to the file name.  

  • The Microsoft.Dynamics.GP.eConnect.serialization - contains classes used to create the required XML documents.
  • Microsoft.Dynamics.GP.eConnect - contains the classes used to integrate these XML documents into Dynamics GP.

Microsoft Dynamics GP eConnect DLLs

Step 1 - Creating a Visual Studio Project

In this example we will create a Windows Console application that will integrate a customer record into Dynamics GP.  The code comes from the samples installed with eConnect in the "C:\Program Files (x86)\Microsoft Dynamics\eConnect 12.0\eConnect Samples\VB DOT NET Console Application" folder. 

Start by opening Visual Studio and then click on File >> New Project.  Select Windows from the installed templates and then Console Application. Enter a name for your project at the bottom and then click on "OK."

Step 2 ...

FREE Membership Required to View Full Content:

Joining gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here

About Gloria Braunschweig

Gloria has experience across the full spectrum of business operations and management. Decades of experience are documented in the book Rapid Implementation, establishing Gloria as a specialists using Microsoft SQL tools for implementation, integration, and business intelligence related to Microsoft Dynamics GP.

Gloria writes and presents on lean implementation concepts and business management systems for small and mid-size businesses. 

Submitted by mgomezb on Mon, 07/29/2013 - 16:48 Permalink

Nice article. I would also suggest you look at using the eConnect Integration Service as an alternative to the actual .NET assemblies. It allows for creating distributed integrations without having to have eConnect installed everywhere. MG.- Mariano Gomez, MVP

In reply to by anonymous_stub (not verified)

Submitted by wmikeh on Fri, 08/02/2013 - 11:40 Permalink

We will add one more article to this series showing an example of using eConnect with the Integration Service.

In reply to by anonymous_stub (not verified)

Submitted by brad_voth on Tue, 07/09/2019 - 15:06 Permalink

This article is doesn't work for me. I'm too novice to know why. I'm using GP2013 and VS2017. My program stalls at the open form. No Customer.xml is ever created and the Customer002 is never inserted into TWO. Are there any resources that you would recommend to help me create a successful example? If I could create a successful example I'm confident I could then tweak it to work for me...I want to eventually use eConnect to create Inventory Transactions. Thanks, Brad Voth

In reply to by anonymous_stub (not verified)