This project has moved and is read-only. For the latest updates, please go here.

JsonDataContractSerializer vs Json.NET

Jan 4, 2009 at 3:50 PM
How is this different from the JsonDataContractSerilizer included in .NET 3.5?
Mar 22, 2009 at 6:57 PM
I'm actually wondering this myself, only for Silverlight.  Json.NET seems to be able to deal with more types of data.  It also lets you create your own serialization helpers.  However, it is quite a heafty runtime to ship in a Silverlight application--180kb is nothing for a "real" application, but it is a lot for a web application that needs to fire up almost instantly.
Mar 22, 2009 at 9:36 PM
Edited Mar 22, 2009 at 9:36 PM
Keep in mind a Silverlight app is compressed in a zip file. The final size downloaded is closer to 70kb.
Mar 22, 2009 at 10:02 PM
This is true.  I'm still getting a feel for what a good size for a XAP is.  Once you toss in System.Windows.Controls.Data, things can get big :-)  Too bad it wasn't easier to load this stuff on demand.  I know you can do it, but it is still a pain in the arse.

By the way, I will back up what I said above... Json.NET is about the only way you can create custom Json Serializers.  I'm creating one right now, in fact and it is pretty easy.  You can't do that with the stock serializer, can you?