Why was ThomsonReuters.Desktop.SDK.DataAccess.Signed.x64 unlisted from nuget?

evan.lee

Question:

Why was the 64-bit package unlisted and can it still be used in a limited capacity (I only need to request timeseries data for a single instrument)?

Background Details:

From https://www.nuget.org/packages/ThomsonReuters.Desktop.SDK.DataAccess.Signed.x64/ it states "The owner has unlisted this package. This could mean that the package is deprecated or shouldn't be used anymore." but I can still see it still being download regularly (https://www.nuget.org/stats/packages/ThomsonReuters.Desktop.SDK.DataAccess.Signed.x64?groupby=Version).

I'm hoping that even if it is delisted it can still be used to request simple data. The reason is because I made the mistake of building an app using that Data Api not knowing what its limitations were in what data it had access to (https://community.developers.refinitiv.com/questions/67830/how-to-convert-a-rhistory-function-into-a-eikondat.html).

Now I have a 64 bit dependent application (won't run on 86x) which I need to integrate a package that is only 32-bit (https://developers.refinitiv.com/en/api-catalog/eikon/-net-apis-for-use-in-custom-applications/tutorials). I don't want to redo my whole project as a 32-bit application and I'd prefer not to have to create a separate 32-bit project to house this Api in and spin it up when I need specific data not available in the Data Api.

If I can still download and use the unlisted 64-bit version it would save me countless hours of work and prevent my applications complexity from drastically increasing.

Alex Putkov.1

Yes, you can still download and install x64 version of this package from NuGet, but please use v1.8.4 of this package instead of the latest available from NuGet v1.9.1. The latter was produced by an automated build, never tested, and never meant to be released in production. In the package manager use:

Install-Package ThomsonReuters.Desktop.SDK.DataAccess.Signed.x64 -Version 1.8.4