Posted: May 25, 2017 @ 05:28 AM             Msg. 1 of 10

I use api version 3.5.14.1 downloaded from nuget.org and it works.
But now OEC Trader Developer use the 3.5.14.26 version.
I tried to compile my project (C#) using 3.5.14.26 but does not work.
Is the 3.5.14.1 the last version for external projects? or am I wrong?

Thank you.

Posted: May 25, 2017 @ 09:18 AM             Msg. 2 of 10

Hello,

We upload OECAPI to nuget only for major versions. You can take the latest API version from OECTrader.
>I tried to compile my project (C#) using 3.5.14.26 but does not work.
We rarely change public interface of API. What errors do you have?
Edited by VPfau on May 25, 2017 09:25 AM

Posted: May 25, 2017 @ 10:01 AM             Msg. 3 of 10

I'm using the framework 4.5.2, I created a new project in VB (Windows form), I added references to APIs and I compiled. Visual Studio (2013) fails to compile but it does not report any specific error. He only tells me that he can not compile because there are some mistakes. But there is nothing on my list of errors, and there are no lines of code written by me, just the form and API references.

Then I did the same thing with a C# project (always windows form) and it worked.

So there must be something that does not work with VB.net.

Posted: May 25, 2017 @ 10:51 AM             Msg. 4 of 10

I tried adding the three DLLs one at a time to the references. Compiling fails when I add Commlib.dll (Api.dll and Protosharp.core.dll already added). So the problem is in Commlib that for any reason it is not compatible with VB.net.

Posted: May 25, 2017 @ 11:41 AM             Msg. 5 of 10

I tried replacing CommLib with the old version (distributed with the API 3.5.14.1) and the compilation also works in VB.net. So I confirm that the problem is in CommLib.

Posted: May 25, 2017 @ 12:49 PM             Msg. 6 of 10

The build could not fail silently.
Download the latest Trader app, take OECAPI and related dlls from there. Do not mix dll's.

I'll make a test VB.NET project for you

Posted: May 25, 2017 @ 12:58 PM             Msg. 7 of 10

Yes sure! I do not mix dll's. it was just a test.

Posted: May 25, 2017 @ 02:54 PM             Msg. 8 of 10

Check this out:
https://www.dropbox.com/s/uc1u7j18lu59zzx/screenshot0161.PNG?dl=0
Test VB.NET project which connects to API environment. No issues for me. The file with compiled binaries and referenced assemblies
https://www.dropbox.com/s/0rmfim4n9nfixw1/TestVBProject.zip?dl=0

Posted: May 25, 2017 @ 05:32 PM             Msg. 9 of 10

Even with your project, I continue to have the same problem.

I'm using Visual Studio 2013 and framework 4.5.2.
Instead, you used the framework 4.6 and, what version of Visual Studio?

The problem may be the version of the Framework or the Visual Studio version.
Please try to test your project using Framework 4.5.2 and, if possible, Visual Studio 2013.
Edited by MFrasson3344 on May 25, 2017 05:33 PM

Posted: May 25, 2017 @ 06:17 PM             Msg. 10 of 10

I found the problem. In the references I removed "System.Xml.Linq" and now your project is compiled successfully. There seems to be an ambiguous reference that the compiler fails to solve. So please, try to investigate about this conflict between System.Xml.Linq and your dlls (in particolar CommLib).


Edited by MFrasson3344 on May 25, 2017 06:17 PM
Edited by MFrasson3344 on May 25, 2017 06:38 PM