Relax our restrictions on Newtonsoft major versions

[jeffhollan]

A few people running into issues when they try to pull down a package that has Newtonsoft 12 requirements as a transitive dependency. While users can get around this today by explicitly pulling down a higher version of Newtonsoft 12 (which will be honored and work in v2 functions), it still leads to a bit of customer confusion. A potential option is to relax our restriction on Newtonsoft 11 so NuGet doesn't complain when this transitive dependency mismatch surfaces.

Related to Azure/azure-functions-host#4049

[metrodeveloper]

Both V1 and V2 should support JSON.NET >9.01 or JSON.NET > 11.0.2, not =

[nicholasdoyle]

I am running into issues trying to use newtonsoft 12.0.2. The runtime is loading 11, even when i explicitly pull 12 into my az functions 2.0 project. I am encountering an exception running JsonConvert.SerializeObject (which is fixed in v12.0.1) and can see the exception.TargetSite.Module is using 11.

I can see both are loaded, but runtime version is being used for this invocation of JsonConvert.
'func.exe' (CoreCLR: clrhost): Loaded '...\AppData\Local\AzureFunctionsTools\Releases\2.22.0\cli\Newtonsoft.Json.dll'.
'dotnet.exe' (CoreCLR: clrhost): Loaded '...\.nuget\packages\newtonsoft.json\12.0.2\lib\netstandard2.0\Newtonsoft.Json.dll'.

[bartdk-be]

Fabio Cavalcante (@fabiocav) : Can you make a preview build and push it to nuget in order to validate your fix ? Current version still has a fixed version (.11). Thanks !

[fabiocav]

nicholasdoyle can you please open a separate issue at https://github.com/Azure/azure-functions-host/issues with the details so that can be investigated?

[PureKrome]

Fabio Cavalcante (@fabiocav) this existing issue can be used by nicholasdoyle IMO.

🚀 🍰

[brandonh-msft]

🎉

[AartBluestoke]

Fabio Cavalcante (@fabiocav) Is this actually resolved? The linked pr is simply relaxes the library requirement, but that will cause horrible to diagnose runtime failures.
If i understand things correctly At runtime the 11.x is what is loaded by the functions runtime, so if I actually use any functionally except from the 11.x version this will be a runtime failure.
Given that protects will typically version change (11->12 in this case) if they use a new feature, then can you confirm that if they did, would things exception?