-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serialization between dotnet core clusternode and framework clusternode does not work properly #108
Comments
The issue is not just related to Dictionary, but I can confirm it also happens with ImmutableDictionary and List. |
The issue is more general than I first thought. When a generic type is used and either the generic type itself, or one of its type parameters is defined in mscorlib/System.Private.CoreLib then the deserializer throws an exception on the framework side. |
@NielsHoogeveen Hyperion/src/Hyperion/Extensions/TypeEx.cs Line 215 in 735c49e
incorrect replacement of the assembly name I fixed it in my library that uses wire |
I confirm I get the same issue, the stack trace: File name: 'System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' |
I just tested the same fix. A bunch of unit tests are failing for good reasons, that might not be enough... |
Any chance for fix? That breaks DistributedData feature :( |
I just came across this problem (while deserializing a I just realized that regrettably, Hyperion doesn't appear to be undergoing much development at the moment, with placeholder documentation, no commits in 2019 and barely nine during the previous year. That's a shame because it seems to perfectly fit my project's requirements. Does anyone at @akkadotnet have an update? Are there any plans for continued development? Is it worth using the serializer in new projects or putting together pull requests? |
closed via #116 |
When trying to send a Dictionary from a dotnet core 2.1 cluster node to a framework 4.7.2 cluster node, using Hyperion, it fails to deserialize on the receiving side.
It seems the framework 4.7.2. node tries to deserialize the dictionary referencing the assembly "System.Private.CoreLib", which only exists in dotnet core.
The exception reads:
Cause: System.IO.FileNotFoundException: Could not load file or assembly 'System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
File name: 'System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
A solution that generates this exception can be found here:
https://github.com/NielsHoogeveen/HyperionTest
The text was updated successfully, but these errors were encountered: