-
Notifications
You must be signed in to change notification settings - Fork 173
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
DataContract Compatibility is broken #33
Comments
Sorry, it is a bug. I misunderstood DataContract behavior. I guess this fix rarely affect existing apps, so I will fix on 0.5 beta2. |
I've fixed this issue and pushed now. |
thanks for your reactivity, I'll test it and see how it goes. |
Hi, |
Sorry. I had forgotten to test entire APIs, and I faced member accessibility related issues because serializers do not use reflection in runtime. (...And I faced another private iasue -- new baby was born.) I will tuckle this issue continuously, but it might take a long time to fix. |
I fixed it, so it now supports following classes when the members are marked with [DataMember] or [MessagePackMember] attributes: https://github.com/msgpack/msgpack-cli/blob/0.5/test/MsgPack.UnitTest/Serialization/SerializationTargets.cs |
Hi @kikokikok |
Hi I am trying to use MsgPack on a client project, it contains types where DataMember decorates private properties and not fields. When MsgPack tries to serialize those it fails because it doesn't look for DataMembers on private properties.
Could you maybe help me find out the best way to add support for that in order to be fuly compatible with DataContract specs.
I'm working on the 0.5 beta 1 version / branch
Thank you
Brgrds,
The text was updated successfully, but these errors were encountered: