2 ms·
> The .net framework only got a json serializer recently. What do you mean by recently? I am not a .net user, but this seems quite basic.
by MattGaiser 6y ago
> The .net framework only got a json serializer recently.
What do you mean by recently? I am not a .net user, but this seems quite basic.
- SimonPStevens 6y agogp is probably thinking of system.text.json which was only added to .net core in version 3, which less than a year old. But it's not been high priority to add because of a very well established open source project called JSON.net that has been around for ages. However the full framework has had a different JSON serialiser (DataContractJsonSerialiser) since v3.5 in 2007.
- foepys 6y agoEarly when JSON was new, people were using the JavaScript parser included in .NET to get the values. Then Microsoft build a small JSON parser for their ASP.NET library. But then James Newton-King build JSON.NET and Microsoft eventually switched a lot of their libraries over to it because it was just very good. It could do a lot of stuff very fast with a nice API. Last year Microsoft introduced a new and more efficient way to allocate memory natively into .NET Core 2.0 (Span<T>). Since JSON.NET is still used by .NET Framework that doesn't support the new API, Microsoft created System.Text.Json that includes a new JSON parser that utilizes it. The first Microsoft project to use the new parser by default was ASP.NET Core 3.0.
- deleted 6y ago[deleted]
- vips7L 6y agoHe probably means in the standard library? According to git NewtonSoft.JSON (the defacto standard) has been around since the 2007.