>The same one you're using,
System.Runtime.Serialization.Json.DataContractJsonSerializer in
System.ServiceModel.Web.dll.
Aargh... the good old "adding reference before using" hits again. Time to go
hide under a rock :(
Thanks for the quick response.
Stephan
--
View this message in context:
On Aug 16, 2012, at 11:07 AM, Stephan Steiner wrote:
> Sorry to revive this old thread - but I'm wondering which
> DataContractJsonSerializer you guys are talking about.
The same one you're using,
System.Runtime.Serialization.Json.DataContractJsonSerializer in
System.ServiceModel.Web.dll.
> I
Sorry to revive this old thread - but I'm wondering which
DataContractJsonSerializer you guys are talking about. It can't be the one
from System.Runtime.Serialization.Json (that's the one I'm currently
searching for), right?
I'm in the same boat - deserializing .NET classes.
--
View this messag
On Sep 1, 2011, at 9:44 AM, Nick Randolph wrote:
> The classes that I'm deserializing to are just standard .NET classes, so
> don't think they inherit from Java.Lang.Object.
To the best of my knowledge, types which do not inherit from Java.Lang.Object
should be usable via DataContractJsonSeriali
ists.ximian.com
[mailto:monodroid-boun...@lists.ximian.com] On Behalf Of Jonathan Pryor
Sent: Saturday, 27 August 2011 10:23 PM
To: Discussions related to Mono for Android
Subject: Re: [mono-android] DataContractJsonSerializer on MonoDroid
On Aug 26, 2011, at 10:27 PM, Nick Randolph wrote:
> Does an
On Aug 26, 2011, at 10:27 PM, Nick Randolph wrote:
> Does anyone have a sample of this that works.
I don't have a sample, but I think I know the problem you're seeing. You cannot
currently use DataContractJsonSerializer with types inheriting (directly or
indirectly) from Java.Lang.Object, becaus
Does anyone have a sample of this that works. I've got sample code that works
across WP7 and MonoTouch but bombs out with the MonoDroid. I've updated to the
latest release of MonoDroid, but am targeting Android 2.3. Wondering if there
any known issues. Unfortunately there is no interpretable exc