LiRuochen_WorkFlow/Newtonsoft.Json
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

-Fixed infinite loop error caused by error handling at the end of JSON content

Browse Source
This commit is contained in:
James Newton-King
2012-08-02 20:50:44 +12:00
parent 4e4fdde9c4
commit be82ab9f0b
3 changed files with 116 additions and 74 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Doc/SerializationGuide.aml
+9 -2
View File
@@ -276,13 +276,20 @@
<content>
<!-- Uncomment this to create a sub-section outline
<autoOutline /> -->
<para>Serialization of values that are convertible by a JsonConverter (i.e. CanConvert returns true for its type) is
<para>Serialization of values that are convertible by a <codeEntityReference>T:Newtonsoft.Json.JsonConverter</codeEntityReference>
(i.e. CanConvert returns true for its type) is
completely overridden by the JsonConverter. The test to see whether a value can be converted by a JsonSerializer takes
precedence over all other tests.</para>
<para> JsonConverters can be defined and specified in a number of places: in an attribute on a member, in an attribute
<para>JsonConverters can be defined and specified in a number of places: in an attribute on a member, in an attribute
on a class and added to the JsonSerializer's converters collection. The priority of which JsonConverter is used is the
JsonConverter defined by attribute on a member then the JsonConverter defined by an attribute on a class and finally
any converters passed to the JsonSerializer.</para>
<alert class="note">
<para>Because a JsonConverter creates a new value a converter will not work with readonly properties because there is no way to assign the new
value to the property. Either change the property to have a public setter or place a JsonPropertyAttribute or DataMemberAttribute on the property.</para>
</alert>
</content>
</section>