Closed ibedek closed 10 months ago
@ibedek did you find a workaround for this?
@dhrovat any plan to upgrade the RabbitMQ.Client ?
In the current version we dont upgrade dependent libraries because it would introduce breaking change to some existing customers. However we plan to release new major release in the beginning of next year, where also all dependent libraries will be updated to latest.
@dhrovat will this mentioned update include the https://github.com/sportradar/UnifiedOddsSdkNet (newer version of non-Core version of lib) as well? Thanks.
In the current version we dont upgrade dependent libraries because it would introduce breaking change to some existing customers. However we plan to release new major release in the beginning of next year, where also all dependent libraries will be updated to latest.
Hello. When can we expect new release with updated dependencies? It's already September.
We are in the final stages of testing it internally. The prerelease version should be published next week.
Today the new major release was published. It includes the latest RabbitMq library (v6.5.0)
I've been upgrading our services to net6 (and all other nuget packages in shared projects), which caused feed service to fail to start with TypeInitializationException:
With version 6 of RabbitMQ.Client, ConnectionFactory is changed to sealed (parent of ConfiguretdConnectionFactory), hence exception.
Steps to reproduce:
or overwrite "Sportradar.OddsFeed.SDK.DemoProject.csproj" with following content:
EDIT: One of reasons for upgrade to net6 is end of support for netcore3.1 in few months. Additionally, RabbitMQ.Client in v6 has bunch of performance improvements (and we use it a lot internally on other parts of system)