Hi Tom, that deserialises okay via Json.NET (LINQPad pasted below) --* GK*
[image: image.png]
It's an array of array of strings. But I would just cast it to dynamic. And use
it that waydynamic obj = deseriizeConsole.write(obj[0].id)HthDavySent from my
Samsung Galaxy smartphone.
Original message From: Tom P Date:
18/07/2019 01:19 (GMT+01:00) To: ozDotNet Subject:
JSO
Thanks guys. I ended up
using System.Web.Script.Serialization.JavaScriptSerializer to deserialize
to a dictionary.
Thanks
Tom
On Thu, 18 Jul 2019 at 15:36, djones147 wrote:
> It's an array of array of strings.
>
> But I would just cast it to dynamic. And use it that way
>
> dynamic obj = deser
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 (
> it's worth noting that NewtonSoft Json.NET will NOT be installed by
default as of .Net Core 3.0:
I was preparing an invoice to send to James Newton-King to charge him for
the countless hair-tearing hours of my life wasted trying to get rid of
version conflict errors in my builds. So many wildly
Apparently Mr NewtonSoft is now working for Microsoft on the Json project
;-)
On Wed, 24 Jul 2019 at 14:33, Greg Keogh wrote:
> > it's worth noting that NewtonSoft Json.NET will NOT be installed by
> default as of .Net Core 3.0:
>
> I was preparing an invoice to send to James Newton-King to char
Not sure if this helps anyone, and it is not a silver bullet, but with
versioning conflicts I tend to handle them in the config file under the
tag :
This usually takes care of any versioning issues I have as a result of
adding 3rd party libraries or Nuget packages.
On
Hi
Just my .02c but I have had nothing but problems with microsoft json
serializers.
Davy
On Wed, 24 Jul 2019, 05:33 Greg Keogh, wrote:
> > it's worth noting that NewtonSoft Json.NET will NOT be installed by
> default as of .Net Core 3.0:
>
> I was preparing an invoice to send to James Newton-K
Visual Studio can automatically add these elements to a
project's config file if you want, but if you have dozens of projects then
a real jumble of config files and redirects arises. I hate these spurious
files because they're a clumsy way of hiding real problems. I always
experimentally comment o
