Fix Serialization KeyNotFoundException when looking up serializers #2356
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@ayoung I like it. Seen this come up when working with Akka.Persistence and using Wire only. |
|
@Aaronontheweb Yes. That was precisely my problem. Spent about an hour trying to figure out what was happening. What is the common solution for this problem? Currently I've been having to do dirty things like this in my code to force msbuild not to ignore those dlls. public static readonly Type[] References =
{
typeof (IActorRef),
typeof (Akka.Cluster.Cluster),
typeof (Akka.Serialization.WireSerializer)
}; |
|
Also, its not a NullRefEx. Its a |
A KeyNotFoundException can occur if the serializer dll is not present in the search paths for binaries. This can occure when there is a proj A that depends on B and B depends on Akka. There is no direct reference to any of the serializers in either A or B besides being referenced in HOCON. MSBuild likes to optimize dlls out of the out- put if they are not directly referenced in code.
ayoung
force-pushed
the
fix-serialization-nullrefex
branch
from
9bae11f to
6bd6128
Compare
ayoung
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A
KeyNotFoundExceptioncan occur if the serializer dll is not present in the search paths for binaries. This can occur when there is a proj A that depends on B and B depends on Akka. There is no direct reference to any of the serializers in either A or B besides being referenced in HOCON. MSBuild likes to optimize dlls out of the output if they are not directly referenced in code.