You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The package has been renamed System.Reactive, System.Reactive.Core... etc. You can still download 2.2.5 through Nuget from the command line but if you search "rx-core" you won't find it. In any case it looks like to be current you need to update to the new naming convention and the 3.x version.
The text was updated successfully, but these errors were encountered:
I think with v3 they made it compatible to .NET Core or the .NET Standard Library or whatever they call their new platform. As far as I know there shouldn't be any breaking changes for us so switching should be fine. Thanks for the hint.
I just tried to upgrade one of my home projects to Rx.NET v3, but there's a conflict because RxUI still depends on Rx.NET 2.2.5. Normally the way to solve this is using binding redirects, but because Rx.NET's public key token changed I don't think this is easily doable.
RX-Core has been discontinued on Nuget https://www.nuget.org/packages/Rx-Main/2.2.5
The package has been renamed System.Reactive, System.Reactive.Core... etc. You can still download 2.2.5 through Nuget from the command line but if you search "rx-core" you won't find it. In any case it looks like to be current you need to update to the new naming convention and the 3.x version.
The text was updated successfully, but these errors were encountered: