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
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
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
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
