asp.net - Why microsoft made JavaScriptSerializer obsolete prior to .net 3.5 SP1 and again active after that?

Question

JavaScriptSerializer is not obsolete after .net 3.5 SP1. Should I uses JavaScriptSerializer or the prior recommended DataContractJsonSerializer?. Also why it was made obsolete?

Answer 1

I'd happily use JavaScriptSerializer - but if in doubt, consider a third option - Json.NET. Because it is 3rd party, it is unrelated to the MS decisions... that is a double-edged sword, of course - but it is often easier to get a minor fix applied to a standalone 3rd-party libary.