Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
consider adding TypeNameHandling.All to the Json serialization settings
See original GitHub issueI have a WebJob triggering from a queue message and the message argument is set as an abstract base type. As a result I get an exception saying that I could use a string and handle the serialization myself.
If the serialization settings for both serialize and deserialize had the TypeNameHandling set to All, then I believe the derived objects would be serialized correctly:
new JsonSerializerSettings { TypeNameHandling = TypeNameHandling.All }
Thank you, Paulo
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We could probably expose a hook for the serializer settings to be changed.
@HMoen I haven’t looked at this in a while but I think the only way to get around it is to create several messages for the different derived types (instead of a single one for the base type).