Hello list,
I've been using the DataContractJsonSerializer class and I've noticed there is a behaviour difference between the Mono library used and the .NET Framework with regard to the Nullable<T> type. When deserialising from JSON and a DataMember is not found, and a type is not Nullable, the deserialization fails (expected behaviour.) However, when I replaced the value type (uint, for instance) to Nullable<T>, .NET (4.0) will deserialise the object and set the member to null. My experience with Monodroid to date is that it will still refuse to deserialise the member even if the DataMember is a Nullable<uint>. Is the behaviour deliberate? My workaround has been to set the DataMember on a string instead, and then manually run a ChangeType when the uint is needed as a property. Regards, Joel
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
