question

Upvotes
Accepted
GoGoGroundhog avatar image
40 ●9 ●6 ●10

Switching to Eikon Desktop API from 32bit to 64bit build

Hi!

We are using the Eikon Desktop API (32 bit Nuget package) in our application.
We would like switch to the 64bit package as this would simplify our workflow as our applications require 64 bit Windows anyway, and all other processes are native 64bits already, except the one using the Ekon API.
We are using the Desktop API for realtime subscriptions as well as historic timeseries.
Is there a scenario where swapping out the 32bit package against the 64bit Desktop API would lead to problems?
E.g. if Eikon is installed as a 32bit application (if that is possible at all on a 64bit machine), would the 64bit Desktop API be able to communicate with that 32bit Eikon Terminal?

Thoughts are most welcome,
Cheers
Ingo

eikoneikon-data-apieikon-com-api64-bit32-bit
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

3 Answers

Upvotes
Accepted
Alex Putkov.1 avatar image
39.3k ●77 ●11 ●27

I concur with Zhenya. Eikon application only exists as 32-bit, however 64-bit Eikon .NET SDK on NuGet works perfectly well with 32-bit Eikon.
Unless you have your own 32-bit code or other 32-bit dependencies in your application, you should be able to simply swap 32-bit binaries of Eikon .NET SDK with 64-bit binaries and recompile your application as 64-bit.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
Zhenya Kovalyov avatar image
4.6k ●26 ●7 ●22

Hi Ingo, in my opinion neither should be an issue.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
GoGoGroundhog avatar image
40 ●9 ●6 ●10

Thanks to you both for your helpful answers!

Ingo

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.