web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

eConnect Compatiblity with .NET Core 2.2

(0) ShareShare
ReportReport
Posted on by 7

I am new to Dynamics GP so pardon me for details which doesn't make sense. I am trying to use eConnect dll version 18 on .NET Core 2.2.1 (Standard Library) but apparently I am facing weird issues internally when I call GetEntity method to retrieve the data. The same code works using .NET Framework.

My question is can we use eConnect dll with .NET standard library? Is .NET Framework the only choice for eConnect?

For your reference following are my findings/errors while testing this on .NET Core 2.2.1 .

1) eConnect.GP cannot load ConfigurationManager (fixed adding Nuget package but not sure why i needed to add one. Works fine with .NET framework)

2) eConnect.Gp cannot load Diagnostics.Tracing (fixed by adding Nuget package)

3) Object reference not set to instance of object on eConnectGP exception handler following is the stack trace. (Cannot fix this)

at Microsoft.Dynamics.GP.eConnect.EventLogHelper.AddExceptionHeader(String action, Object[] inputParameters, StringBuilder errorString)
at Microsoft.Dynamics.GP.eConnect.EventLogHelper.CreateEventLogEntry(Exception exception, String action, Object[] inputParameters)
at Microsoft.Dynamics.GP.eConnect.eConnectMethods.GetEntity(String connectionString, String sXML)

follwing is the eConnect XML that is passed to GetEntity method

<?xml version="1.0"?><eConnect xmlns:xsi="">www.w3.org/.../XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><RQeConnectOutType><eConnectProcessInfo xsi:nil="true" /><taRequesterTrxDisabler_Items xsi:nil="true" /><eConnectOut><DOCTYPE>Vendor</DOCTYPE><OUTPUTTYPE>2</OUTPUTTYPE><FORLIST>1</FORLIST></eConnectOut></RQeConnectOutType></eConnect>

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    MG-16101311-0 Profile Picture
    26,225 on at

    Yup. The eConnect assembly was written prior to the days of .NET Core 2.2, so I don't think you can reference it in your .NET Core project directly without creating a NuGet package (which you did) and even so, I don't think you will achieve any degree of stability.

    Another thing you could try is to wrap the eConnect stored procs directly in .NET Core, but that in itself is quite the project, but probably worth a try.

  • ssp Profile Picture
    7 on at

    Thanks Mariano!!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans