[CLOSED] Using JSON.Serialize() and JSON.Deserialize()

[vadym.f]

Hi,

Could you give me some pointers on the proper usage of JSON serialization methods? Both Serialize and Desirialize work OK for me by default as long as I don't have a hierarchy of derived classes. However, that's where the challenges start. It seems as though JSON.Deserialize() requires a properly created list of Newtonsoft JsonConverter objects or an instance of IContractResolver in order to be able to handle inherited classes.

I've looked at the Newtonsoft documentation and examples to help me get on track at
http://james.newtonking.com/projects...meHandling.htm
http://james.newtonking.com/projects...nConverter.htm
http://james.newtonking.com/projects...ctResolver.htm

Any hint or directions would be highly appreciated. Please advise if more info is required.

[Daniil]

Hi Vadym,

However, that's where the challenges start. It seems as though JSON.Deserialize() requires a properly created list of Newtonsoft JsonConverter objects or an instance of IContractResolver in order to be able to handle inherited classes.

To be able to handle inherited classes? Sorry, I don't not quite follow you. Could you, please, clarify?

Are you asking how to create custom converters?

[vadym.f]

Hi Vadym,



To be able to handle inherited classes? Sorry, I don't not quite follow you. Could you, please, clarify?

Are you asking how to create custom converters?

I think so. Do you have any example using JSON.Serialize() and Deserialize() similar to this?
http://james.newtonking.com/projects...meHandling.htm

[Daniil]

Well, there is no an overloaded version of the Serialize method with this signature.

string jsonTypeNameAll = JsonConvert.SerializeObject(stockholder, Formatting.Indented, new JsonSerializerSettings
{
    TypeNameHandling = TypeNameHandling.All
});

The Json class is a set of wrappers for Json.NET.
http://svn.ext.net/premium/branches/...t/Util/JSON.cs

It defines the wrappers which are convenient to use within Ext.NET and, certainly, in a developer's application. But it doesn't reflects all of possible overloaded version of the JsonConvert.SerializeObject method.

You could use the JsonConvert.SerializeObject method directly if needed. If you do need (or just want) use the JSON.Serialize method, you might need to implement a custom JsonConverter. There is a lot of custom JsonConverters used in Ext.NET. They are in this folder.
http://svn.ext.net/premium/branches/...sonConverters/

[Daniil]

By the way, the JSON class has been improved in Ext.NET v2. There are the overloaded methods which takes a JsonSerializeSettings instance.

Also there are the GloballSettings и RequestSettings properties to manage serialization options in a global manner.

[vadym.f]

It seems that Newtonsoft's SerializeObject() method isn't very robust when handling a JSON object built on the client side. I manually build a JSON object and have to assign the $type property in the form of $type="FullyQualifiedTypeName, AssemblyName" for all derived classes, which SerializeObject expects to be present. However, if this property isn't the first in the object state, it's somehow ignored and only parent class properties are serialized. I'm not sure how to make the $type property appear first in the client object state. I do realize this may not be directly related to Ext.Net but any hint would be appreciated.

The code below works only if the $type property comes first in the JSON property stack.

string jsonTypeNameAll = JsonConvert.SerializeObject(stockholder, Formatting.Indented, new JsonSerializerSettings
{
    TypeNameHandling = TypeNameHandling.All
});

[geoffrey.mcgill]

It seems that Newtonsoft's SerializeObject() method isn't very robust when handling a JSON object built on the client side. I manually build a JSON object and have to assign the $type property in the form of $type="FullyQualifiedTypeName, AssemblyName" for all derived classes, which SerializeObject expects to be present. However, if this property isn't the first in the object state, it's somehow ignored and only parent class properties are serialized. I'm not sure how to make the $type property appear first in the client object state. I do realize this may not be directly related to Ext.Net but any hint would be appreciated.

The code below works only if the $type property comes first in the JSON property stack.

string jsonTypeNameAll = JsonConvert.SerializeObject(stockholder, Formatting.Indented, new JsonSerializerSettings
{
    TypeNameHandling = TypeNameHandling.All
});

It might be best to post Json.NET specific questions on the Json.NET related forum. Or, post a simplified .aspx code sample that demonstrates the whole scenario.

[vadym.f]

Found a robust solution at http://stackoverflow.com/questions/8...a-list-of-base. Please mark this thread as closed.