Question

It just strikes me that What can JSON.net library do in special that a JavaScriptSerializer class does not?

1. Is it worth including in a large enterprise application that talks through SOAP webservices and javascript?

2. What performance gain/ development gain i get by including such libraries in the project?

3. Are there similar libraries that aid in object serialization/ deserialization faster, better and smarter?

Answer 1

1. Yes it is. Absolutely. Just because something comes by default with the .NET framework built by Microsoft it does not mean that it’s the best thing to use. The size of an application, nor where it’s deployed, in my view is hardly a determining factor of whether a library like JSON.net should be used. Look at your own needs and use that as the driver, not the size of your app.
2. Substantial. JSON.net is really fast, has a lot more features and is a much “friendlier” API to use. I wouldn’t hesitate recommending it for use in any application. I have personally used it in Enterprise applications, open source libraries and WP7 games.
3. There are lots of similar libraries. JsonFx is one. Is it faster, better and smarter? Yes and no, yes and no, and yes and no respectively. There is no golden bullet for this kind of thing. You should investigate your needs and figure out which one suits you. I can almost guarantee that if you’re happy to use the out-of-the-box JavascriptSerializer you won’t (can’t!) be disappointed with the features and speed of either of these other options.

HTH.