JsonSerializer has a number of properties on it to customize how it serializes JSON. These can also be used with the methods on JsonConvert via the JsonSerializerSettings overloads.
DateFormatHandling controls how dates are serialized.
By default Json.NET writes dates in the ISO 8601 format, e.g. "2012-03-21T05:40Z".
Dates are written in the Microsoft JSON format, e.g. "\/Date(1198908717056)\/".
MissingMemberHandling controls how missing members, e.g. JSON contains a property that isn't a member on the object, are handled during deserialization.
By default Json.NET ignores JSON if there is no field or property for its value to be set to during deserialization.
Json.NET errors when there is a missing member during deserialization.
ReferenceLoopHandling controls how circular referencing objects, e.g. a Person object referencing itself via a Manager property, are serialized.
The Equals(Object) method is used to test whether an object is in a circular reference. By default Object.Equals(Object) will test whether the references are equal for reference types and private and public values are equal for value types. Classes and structs can override this method.
By default Json.NET will error if a reference loop is encountered (otherwise the serializer will get into an infinite loop).
Json.NET will ignore objects in reference loops and not serialize them. The first time an object is encountered it will be serialized as usual but if the object is encountered as a child object of itself the serializer will skip serializing it.
This option forces Json.NET to serialize objects in reference loops. This is useful if objects are nested but not indefinitely.
ReferenceLoopHandling can be used as an argument when calling the serializer, it can be set on an object's properties or a collection's items using ItemReferenceLoopHandling, customized on a property with ReferenceLoopHandling or a property's object properties or collection items using ItemReferenceLoopHandling.
NullValueHandling controls how null values on .NET objects are handled during serialization and how null values in JSON are handled during deserialization.
By default Json.NET writes null values to JSON when serializing and sets null values to fields/properties when deserializing.
Json.NET will skip writing JSON properties if the .NET value is null when serializing and will skip setting fields/properties if the JSON property is null when deserializing.
NullValueHandling can also be customized on individual properties with JsonPropertyAttribute.
By default Json.NET will write a field/property value to JSON when serializing if the value is the same as the field/property's default value. The Json.NET deserializer will continue setting a field/property if the JSON value is the same as the default value.
Json.NET will skip writing a field/property value to JSON if the value is the same as the field/property's default value, or the custom value specified in DefaultValueAttribute if the attribute is present. The Json.NET deserializer will skip setting a .NET object's field/property if the JSON value is the same as the default value.
DefaultValueHandling can also be customized on individual properties with JsonPropertyAttribute.
ObjectCreationHandling controls how objects are created and deserialized to during deserialization.
By default Json.NET will attempt to set JSON values onto existing objects and add JSON values to existing collections during deserialization.
Same behaviour as auto.
Json.NET will always recreate objects and collections before setting values to them during deserialization.
ObjectCreationHandling can also be customized on individual properties with JsonPropertyAttribute.
TypeNameHandling controls whether Json.NET includes .NET type names during serialization with a $type property and reads .NET type names from that property to determine what type to create during deserialization.
The value of the $type property can be customized by creating your own SerializationBinder.
By default Json.NET does not read or write type names during deserialization.
Json.NET will write and use type names for objects but not collections.
Json.NET will write and use type names for collections but not objects.
Json.NET will check whether an object/collection matches its declared property and writes the type name if they do not match, e.g. a property with a type of Mammal has a derived instance of Dog assigned. Auto will ensure that type information isn't lost when serializing/deserializing automatically without having to write type names for every object.
Json.NET will write and use type names for objects and collections.
TypeNameHandling can be used as an argument when calling the serializer, it can be set on an object's properties or a collection's items using ItemTypeNameHandling, customized on a property with TypeNameHandling or a property's object properties or collection items using ItemTypeNameHandling.
FormatterAssemblyStyle controls how type names are written during serialization.
By default Json.NET writes the partial assembly name with the type, e.g. System.Data.DataSet, System.Data. Note that Silverlight and Windows Phone are not able to use this format.
Json.NET will write the full assembly name, including version number, culture and public key token.
Read more about the valid values at FormatterAssemblyStyle.
The SerializationBinder is used to resolve type names to a .NET type.
Read more about the serialization binder here: SerializationBinder
ConstructorHandling controls how constructors are used when initializing objects during deserialization.
By default Json.NET will first look for a constructor marked with the JsonConstructorAttribute, then look for a public default constructor (a constructor that doesn't take any arguments), then check if the class has a single public constructor with arguments and finally check for a non-public default constructor. If the class has multiple public constructors with arguments an error will be thrown. This can be fixed by marking one of the constructors with the JsonConstructorAttribute.
Json.NET will use a classes private default constructor before constructors with arguments if available.
This is the collection of JsonConverters that will be used during serialization and deserialization.
A JsonConverter allows JSON to be manually written during serialization and read during deserialization. This is useful for particularly complex JSON structures or for when you want to change how a type is serialized.
When a JsonConverter has been added to a JsonSerializer it will be checked for every value that is being serialized/deserialized using its CanConvert to see if it should be used. If CanConvert returns true then the JsonConverter will be used to read or write the JSON for that value. Note that while a JsonConverter gives you complete control over that values JSON, many Json.NET serialization features are no longer available like type name and reference handling.
JsonConverters can be used as an argument when calling the serializer, it can be set on an object or property using JsonConverterAttribute, it be set on an object's properties or a collection's items using ItemConverterType, or a property's object properties or collection items using ItemConverterType.
To create your own custom converter inherit from the JsonConverter class. Read more about the built-in JsonConverters below:
Internally for every .NET type the JsonSerializer will create a contract of how the type should be serialized and deserialized, based on type metadata and attributes applied to the class. Specifying a custom IContractResolver allows the creation of contracts to be customized.
Read more about Contract Resolvers here: Serialization using ContractResolver
The Json.NET serializer supports logging and debugging using the ITraceWriter interface. By assigning a trace writer you can debug what happens inside the Json.NET serializer when serializing and deserializing JSON.
Read more about TraceWriters here: Debugging with Serialization Tracing
The Error event can catch errors during serialization and either handle the event and continue with serialization or let the error bubble up and be thrown to the application.
Read more about error handling here: Serialization Error Handling