{"id":5041,"date":"2016-01-12T09:36:17","date_gmt":"2016-01-12T09:36:17","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/dotnet\/2016\/01\/12\/the-week-in-net-1122016\/"},"modified":"2021-09-30T13:58:38","modified_gmt":"2021-09-30T20:58:38","slug":"the-week-in-net-1122016","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/the-week-in-net-1122016\/","title":{"rendered":"The week in .NET – 1\/12\/2016"},"content":{"rendered":"

To read last week’s post, see The week in .NET – 1\/5\/2016<\/a>.<\/p>\n

<\/a>On.NET<\/h2>\n

Last week, we had Mads Torgersen on the show<\/a> to talk about language design in general, and C# in particular. This week, we’ll talk to Jonathan Chambers from the Unity 3D<\/a> team about game engines, and using .NET to target iOS, Android, or even the Web. Please send me your questions ahead of time, or attend the show and ask them on the chat. Tune in on Thursday, at 10:00AM PST<\/a> to view the show live!<\/p>\n

<\/a>Package of the week #1: JSON.NET 8<\/h2>\n

JSON.NET<\/a> needs no introduction, as it is the recommended library to serialize and deserialize JSON in .NET. James Newton-King just released version 8.0<\/a> with lots of bug fixes, and great performance improvements. To improve perf on an already very fast library, James introduced new ways in which a JSON.NET user can avoid memory allocations. Instead of allocating new buffers as needed, the new code uses pools of buffers:<\/p>\n