For those that are looking at moving forward with .Net Core, it's worth noting that NewtonSoft Json.NET will NOT be installed by default as of .Net Core 3.0: https://github.com/dotnet/announcements/issues/90
Rather, there's a new System.Text.Json serializer that's about 20% faster than Json.NET (but isn't as feature rich). You can always switch back to Json.Net by installing it via NUGET if you need these features. https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-core-3-0-preview-5/ On Mon, 22 Jul 2019 at 13:47, Tom P <tompbi...@gmail.com> wrote: > Thanks guys. I ended up > using System.Web.Script.Serialization.JavaScriptSerializer to deserialize > to a dictionary<string, MyCustomObject>. > > Thanks > Tom > > > On Thu, 18 Jul 2019 at 15:36, djones147 <djones...@gmail.com> wrote: > >> It's an array of array of strings. >> >> But I would just cast it to dynamic. And use it that way >> >> dynamic obj = deseriize >> >> Console.write(obj[0].id) >> >> Hth >> >> Davy >> >> >> >> Sent from my Samsung Galaxy smartphone. >> >> -------- Original message -------- >> From: Tom P <tompbi...@gmail.com> >> Date: 18/07/2019 01:19 (GMT+01:00) >> To: ozDotNet <ozdotnet@ozdotnet.com> >> Subject: JSON deserialize >> >> Hi all >> >> Noob question here as it seems my brain is not working at all. >> >> I have json like this: >> >> { >> “Some GUID”: { >> “Id”: “Some GUID”, >> “Property1”: “abc”, >> “Property2”: 123.45, >> “Property3”: false >> }, >> “Another GUID”: { >> “Id”: “Another GUID”, >> “Property1”: “def”, >> “Property2”: 456.10, >> “Property3”: true >> } >> } >> >> I can’t seem to work out how to deserialize this with Json.NET. Any hints >> to trigger my brain to wake up? Quite embarrassing. >> >> Thanks >> Tom >> -- >> Thanks >> Tom >> >
