You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to at least lower the version of the Newtonsoft.Json dependency to 8.0.3? We are using Unity 2017.4 LTS in the project because of the NET scripting backend and HoloLens support and currently all our Unity stuff breaks because this NuGet bumps the Newtonsoft.Json to 10.x and the UnityEngine does not support it apparently - there is a TypeLoadException coming from UnityEngine.Internal.
I know this could be solved in WPF where it is possible to have multiple versions of the same assembly loaded at the same time in different app domains and reference the correct version using an alias, but as far as I know there is no way to do it in UWP.
Thanks for the info @jimm98y. I'm not sure if downgrading a dependency would have any other impact in other areas/scenarios (@azchohfi any thoughts?) and if there's anything we're using from newer versions or not. We'll take a look.
I think it's a matter of testing and seeing what breaks, and if forcing to upgrade to a newer Newtonsoft.Json does not break the current code we use from it. There is some investigation that needs to be done for this.
Uh oh!
There was an error while loading. Please reload this page.
Would it be possible to at least lower the version of the Newtonsoft.Json dependency to 8.0.3? We are using Unity 2017.4 LTS in the project because of the NET scripting backend and HoloLens support and currently all our Unity stuff breaks because this NuGet bumps the Newtonsoft.Json to 10.x and the UnityEngine does not support it apparently - there is a TypeLoadException coming from UnityEngine.Internal.
I know this could be solved in WPF where it is possible to have multiple versions of the same assembly loaded at the same time in different app domains and reference the correct version using an alias, but as far as I know there is no way to do it in UWP.
Originally posted by @jimm98y in #889 (comment)
The text was updated successfully, but these errors were encountered: