GP serialization from .net hosted site

(1) Share

Report

Posted on by Community Member

I'm trying to get the Microsoft.Dynamics.GP.eConnect.Serialization.dll running on a .net website.

I can get the 64 bit dll functioning on my development PC by setting the Tools/Options/Projects/Web Projects 'Use 64 bit version...' But haven't found a way to get it running on the production website. It always throws the "incorrect format" error anytime it attempts to access the dll indicating a 32/64 bit mismatch.

I can get past the "incorrect format" error using the 32 bit dll functioning on the production website. But both development and production tells me I can't resize the eConnect.UPRCreateEmployeeType array in order to add additional entries.

Does anyone have this dll working on a .net website?

thanks

Note: our GP is hosted on a third parties site and we are required to first create the XML file, then ftp it to the third party server where an application will read the XML and perform the actual interface into GP.

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Almas Mahfooz 11,009 User Group Leader on at

Like (0)

Report

Try the resolutions in '.NET Assembly Incorrect Format Error' post. it worked for me when working for VSTools project.

http://cknotes.com/tag/64-bit/

Was this reply helpful? Yes No
Tim Wappat 5,711 on at

Like (0)

Report

I use x86 specific platform to get around this.

I think this is the same as what Almas said...

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks for your response. This is what I did to get a c# winforms application properly running. But I can find no method of porting this setting from VS Express for Web to the actual web site. So I can get it running from with my development's VS environment - but haven't found a way to get the hosted web site to use the same settings.

Was this reply helpful? Yes No
Tim Wappat 5,711 on at

Like (0)

Report

I use WCF "microservice(s)" to handle the GP interaction and keep that separated from the website code so the website does not directly reference any GP assemblies. So that architecture avoids this problem.

Tim.

Was this reply helpful? Yes No