New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate: 122 dependencies in Newtonsoft.Json 10.0.2 when adding to UWP app #1291
Comments
I believe it is because Json.NET is referencing .NET Core 1.1 libs (NETStandard.Library 1.6.1) and UWP is still 1.0. The 1.0 libs are being replaced with 1.1 libs from NuGet Either use 9.0.1 until UWP moves to .NET Core 1.1 and those NuGet packages are bundled by default or just accept that there are a lot of NuGet packages. As soon as you reference another package that uses NETStandard.Library 1.6.1 then the same thing will happen. I'm not a UWP expert. IMO you should raise this with MS if lots of NuGet packages concern you. |
I should maybe rephrase the issue to: Do not force .NET Core libs 1.1 in UWP projects
So it's possible that installing Newtonsoft.Json v10.0.2 can break the .NET Native compilation in UWP apps? |
No idea. If it does then that is a bug for the UWP team. |
Newtonsoft.Json supports .NET Standard 2 now. You should be able to use that with new versions of UWP without a lot of references. |
When adding previous version 9.0.1 to UWP app, it added only one required dll and that was all, working as expected.
Suddenly when I updated to v10.0.2, this package has transitive dependency on 122(!) other NuGet packages, that are part of the NETStandard.Library and Microsoft.CSharp. The full list of dependencies is at the bottom.
I don't really think Newtonsoft.Json should require this huge list of dependencies when targeting the UWP platform, specifically Microsoft.NETCore.UniversalWindowsPlatform 5.3.2.
122 dependencies in Newtonsoft.Json 10.0.2
The text was updated successfully, but these errors were encountered: