Thanks Jonathan, While it may not be my exact case, I think the code should be related. Following the comments, it seems like there was a change made in https://bugzilla.xamarin.com/show_bug.cgi?id=2843 which was applied to master and subsequently should be in the 4.2 series. I'll try the test again on the 4.1 alphas and see if the problem still exists.
Yes, I understand that WCF is still in alpha, so bugs like that are bound to occur. I also note that Atsushi's workaround (in #2843) is what I'm currently doing in the meantime and does work for most cases (main thing is just making sure that data will survive the string <=> UDT round-trip). Regards, Joel > -----Original Message----- > From: monodroid-boun...@lists.ximian.com [mailto:monodroid- > boun...@lists.ximian.com] On Behalf Of Jonathan Pryor > Sent: Friday, 11 May, 2012 4:35 AM > To: Discussions related to Mono for Android > Subject: Re: [mono-android] DataContractJsonSerializer and Nullable<T> > > On May 9, 2012, at 9:38 PM, Joel Low wrote: > > 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. > > I suspect that you're seeing this, which mentions DataContractSerializer: > > https://bugzilla.xamarin.com/show_bug.cgi?id=3258 > > - Jon > > _______________________________________________ > Monodroid mailing list > Monodroid@lists.ximian.com > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
