- New feature - Added TypeNameHandling.Auto to automatically write the type name when a value doesn't match the declared type
- New feature - Added CLSCompliant attributes
- New feature - Added Required.Always attribute validation when writing JSON
- New feature - Added DateTimeKindHandling to BsonWriter to control how a DateTime is converted prior to being serialized
- New feature - Added SerializeCompilerGeneratedMembers to DefaultContractResolver to control serializing compiler generated fields
- Change - Improved OverflowException message for integer values larger than an Int64
- Change - Added interfaces, structs and enums as valid targets of JsonConverterAttribute
- Change - Added structs as a valid target of JsonObjectAttribute
- Change - Improved default null and value handing when JSON value is not compatible with property value
- Change - Serialization attributes now supported in .NET 2.0
- Change - HtmlColorConverter and System.Drawing.dll dependency removed
- Fix - Fix reading hexadecimal numbers that contain an e
- Fix - Generic simple type names no longer include full qualified assembly information for nested generate types
- Fix - Corrected culture invariance issues
- Fix - Correct incorrect BSON string reading for multi-byte characters
- Fix - Fix error when converting a JValue to a compatible type
- Fix - Fix security exception when generating simple type names on Silverlight
- Fix - JsonProperty now inherited on overriden properties
- Fix - JTokenReader.ReadAsBytes no longer errors when reading null token value
|
Thanks for supporting pocket pc but in this version when deserialize object with property DataSet, throws "Unexpected token when deserializing object: StartObject" Serialization exception. In 4.0 release 4 this bug had fixed. Unfortunately that verison does not include pocketpc build. Can you fix that bug for pocket pc build ?
by
berkcosar
on
Dec 1 2011 at 2:46 PM
I use this with the DataTable Grid its Great
by
jasonmichaelrober
on
Apr 9 2011 at 5:17 AM
The best -> So well documented too! I havn't seen a library this well documented since, well never. Thank you. Now I dont have to google around for working examples. It inludes a .chm file.
by
la2texas
on
Dec 31 2010 at 4:14 PM
Nice! Very easy to use.
by
an00bis
on
Dec 28 2010 at 6:37 PM
Saved me loads of time. Well done!
Cheers,
Daniel
by
DanielVaughan
on
Dec 12 2010 at 10:49 PM
Amazing library : after having tried to get the job done by the official JSON contract serializer in vain, I've been able to obtain the expected behaviour with Json.Net with one line of code !
by
serious
on
Nov 9 2010 at 4:45 PM
This is a great example of what a useful library should look like.
by
MrTyzik
on
Oct 21 2010 at 11:05 PM
Great JSON library. I especially like the ability to (de)serialize using the CamelCasePropertyNamesContractResolver which allows for idiomatic capitalization where JavaScript properties start with a lowercase and C# properties start with an upper case. You can do this with the Microsoft libraries, but the approach here just seems more elegant.
by
markkanof
on
Oct 12 2010 at 4:35 PM
Very stable and well designed JSON-Library. You have different options for (de)serialization so it's always possible to tweak the produced JSON as you want.
by
sentinel101
on
Oct 11 2010 at 8:18 PM
ok,good!!!!!!!!!~~~~~~~~~~~~~~~~~
by
thhtc
on
Oct 6 2010 at 4:03 PM
asdfasdfasdfa
by
felix888
on
Sep 19 2010 at 8:15 AM