Trying to use DSS SDK Seach and I am getting a System.TypeLoadException Exception
Trying to use DSS SDK Seach in project targeting .Net Standard 2.1 and I am getting a System.TypeLoadException Exception
Tried changing the target to .Net Framework 4.5.1 and I am getting the same exception
I copied and referenced all the DLLs as directed in the Getting Started docs.
System.TypeLoadException: Could not load type 'Microsoft.OData.Edm.Library.EdmElement' from assembly 'Microsoft.OData.Edm, Version=7.5.0.20627, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.\r\n at Microsoft.OData.Client.DataServiceContext..ctor(Uri serviceRoot, ODataProtocolVersion maxProtocolVersion)\r\n at ThomsonReuters.Dss.Api.DssDataServiceContext.Initialize(Boolean sampleMode, String clientSessionId) in d:\\BuildAgent\\work\\5085137dd0574126\\src\\ServiceLayer\\ServiceLayer.Client\\Core\\DssDataServiceContext.cs:line 100\r\n at ThomsonReuters.Dss.Api.DssDataServiceContext..ctor(Uri serviceRoot, String userName, String passWord, Boolean sampleMode, String clientSessionId) in d:\\BuildAgent\\work\\5085137dd0574126\\src\\ServiceLayer\\ServiceLayer.Client\\Core\\DssDataServiceContext.cs:line 70\r\n at ThomsonReuters.Dss.Api.Search.SearchContext..ctor(Uri serviceRoot, String userName, String password, Boolean sampleMode, String clientSessionId)
Best Answer
-
DSS SDK doesn't support .NET standard. It supports .NET Framework 4.5+, mentioned here.
The version of Microsoft.OData.Edm.dll in the DSS SDK is 6.15.
From the error message, the version of Microsoft.OData.Edm is 7.5.0.20627. I get the same error if I use the same version (7.5.0.20627).
Unhandled Exception: System.TypeLoadException: Could not load type 'Microsoft.OData.Edm.Library.EdmElement' from assembly 'Microsoft.OData.Edm, Version=7.5.0.20627, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
at Microsoft.OData.Client.DataServiceContext..ctor(Uri serviceRoot, ODataProtocolVersion maxProtocolVersion)
at ThomsonReuters.Dss.Api.DssDataServiceContext.Initialize(Boolean sampleMode, String clientSessionId) in d:\BuildAgent\work\5085137dd0574126\src\ServiceLayer\ServiceLayer.Client\Core\DssDataServiceContext.cs:line 100
at ThomsonReuters.Dss.Api.DssDataServiceContext..ctor(Uri serviceRoot, String userName, String passWord, Boolean sampleMode, String clientSessionId) in d:\BuildAgent\work\5085137dd0574126\src\ServiceLayer\ServiceLayer.Client\Core\DssDataServiceContext.cs:line 69
at ThomsonReuters.Dss.Api.Extractions.ExtractionsContext..ctor(Uri serviceRoot, String userName, String password, Boolean sampleMode, String clientSessionId) in d:\BuildAgent\work\5085137dd0574126\src\Api\RestApi.Client\ExtractionsClientApi.generated.cs:line 3851
at DSSTest451.DssClient.ConnectToServer(String dssUserName, String dssUserPassword) in C:\Users\U8009686\source\repos\DSSTest451\DSSTest451\DssClient.cs:line 76
at DSSTest451.Program.Main() in C:\Users\U8009686\source\repos\DSSTest451\DSSTest451\Program.cs:line 30The problem can be solved if I used the Microsoft.OData.Edm.dll version 6.15 in the DSS SDK package.
0
Answers
-
Thanks @jirapongse.phuriphanvichai. I determined that another dependency that I had on Microsoft.Azure.WebJobs.Extensions.Storage was depending on Microsoft.OData.Core >= 7.6.4 which in turn depended on Microsoft.OData.Edm 7.7.2. Fortunately, for the moment at least, I am able to downgrade Microsoft.Azure.WebJobs.Extensions.Storage from 4.0.2 to 3.0.11 to remove the dependency on Microsoft.OData.Edm 7.5.0.20627. I get a waring that "This project may not be fully compatible with your project." but it still seems to work.
However, this is far from being a good solution. Can you tell me when Refinitiv and the DSS SDK will support .net Core? Net Core is the current recommendation from Microsoft for new projects and has been for a while. Not having support for Net Core makes Refinitiv seem out of date and headed towards irrelevant. That is unless the DSS SDK is not the current recommendation from Refinitiv but everything I read on the site so far suggests that the DSS SDK is in fact what you all are telling people to use. Should we instead be rolling our own REST integration?
0 -
Can someone at Refinitiv confirm the current guidance for users who require .Net Standard support? Is there a roadmap for when .Net Standard will be supported.
0 -
I will contact the DSS product team for this question.
0 -
I got a response from the product team that we don’t have a plan to add support of .NET Core to the DSS SDK.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛