Posted: Mar 26, 2014 @ 03:48 PM             Msg. 1 of 4

Hi,

I noticed that the latest OEC Trader Demo installer is named "OEC Trader Demo 3.5.13.2.exe". This is great! I no longer have to dig through "OEC Trader Demo 3.5 (#).exe" files in my Downloads folder to figure out which one is which. I also noticed that it has the file resource set with a matching File version and Product version of 3.5.13.2, so I can double check there in case the name gets changed.

It would be very helpful if the file name of "OEC API COM 3.5.exe" were to also update in the same way, and if it's resource had the file and product versions set. It would be nice if they were incremented like OEC Trader.

I also noticed that the file and product versions of API.dll and CommLib.dll installed by OEC Trader Demo 3.5.13.2.exe are 3.5.13.0 and the file and product versions of Trader.exe is 3.5.13.2. That is pretty handy when trying to figure out which ones go together. I don't know what the .2 means. Maybe you had a few internal builds where all you changed was the UI. That seems like a reasonable way to version it.

Could OECAPICOM.dll be versioned like Trader.exe appears to be, since it is also a consumer of API.dll and CommLib.dll assemblies?

Then we could talk about what version of OECAPICOM.dll we have without looking at a bunch of time stamps and file sizes. I wouldn't expect them to have the exact same version down to the build level, but if it had the same major.minor.patch we could feel more confident that we have the same feature set as OEC API and OEC Trader.

PS. This doesn't have anything to do with the COM exported UUID versioning. Just simply file versions for OECAPICOM.dll, OEC API COM 3.5.exe installer, and expanding the naming of the installer to match the OECAPICOM.dll file version.

Thank you for the consideration,

---

--
Jacob Anawalt

Posted: Jun 23, 2014 @ 02:58 PM             Msg. 2 of 4

I noticed today that the current OEC Trader, v. 3.5.14.3, has its API.dll versioned at 3.5.13.0.

The API.dll version number from the most current OEC API COM.exe is 3.5.12.0. Despite the version number differences, the sizes of the two API.dll's are exactly identical. I don't know if that means they are actually the same...

Unfortunately, the current OECAPICOM.dll wrapper of the API.dll is missing functionality that exists in the API.dll. This nearly always seems to be the case. The updates to API.dll that are released by OEC as part of OEC Trader updates are almost never matched with an attending update to OECAPICOM.dll. All COM-based api consumers therefore are forced to work with outdated versions of the api.

Also, it is currently impossible to develop new code using any new OEC API COM API.exe dlls and also maintain existing code using the OEC API COM exe that has the older dlls used by our current users. If the old and new OEC API COM API.exe to had different version numbers, this would not be the case.

We request that OECAPICOM be versioned like Trader.exe. It will greatly assist all COM-based users of your terrific api.

Thanks,

---

CHW

Posted: Jun 26, 2014 @ 09:57 AM             Msg. 3 of 4

Hello,

We will provide versioned OEC API COM library with next update.

Thanks

---

Vitaliy Pfau

Posted: Jun 26, 2014 @ 12:43 PM             Msg. 4 of 4

Great, I look forward to having version numbers on the OECAPICOM installer's file name, the file properties, and on OECAPICOM.dll's properties.



I want to restate that my request didn't have anything to do with the COM exported UUID versioning that I believe is required to have two versions of OEC API COM installed at the same time. Just simply file versions for OECAPICOM.dll, OEC API COM 3.5.exe installer, and expanding the naming of the installer to match the OECAPICOM.dll file version.

If your next version will also have UUID versioning to allow multiple versions to exist, we welcome that as well.

Thank you,

---

--
Jacob Anawalt