Quantcast
Channel: Active questions tagged nuget-package - Stack Overflow
Viewing all articles
Browse latest Browse all 3067

Nuget Hell: Cannot reference NuGet package in UWP application due to public key difference

$
0
0

I have a UWP app and a bunch of NETStandard 2.0 libraries. The libraries contains a lot of logic and communication interfaces that I am using in ASP.NetCore and Desktop WPF applications, so I am not going to change them.

I use NuGet packages in the libraries so I could reference those in NetCore and NetFramework projects as well. I would like to reference these packages in the UWP project - cause this is the whole point of this standardization concept isn't it?

For the UWP project this does not work. I have the latest Nuget package of System.ServiceModel.Primitives which is 4.5.3 (DLL version 4.5.0.3 - don't ask why) and PublicKeyToken is b03f5f7f11d50a3a - this can be referenced in every project except UWP.

Regardless of every attempt:- I have installed the Nuget package for the project- I have referenced the version explicitly in the CSPROJ file- I have removed every other reference to SDK file version

But still, the UWP project looks for the dll in

C:\Program Files (x86)\Microsoft SDKs\UWPNuGetPackages\microsoft.netcore.universalwindowsplatform\6.2.8\ref\uap10.0.15138\System.ServiceModel.Primitives.dll

That DLL has version of 4.2.1.1 and the PublicKeyToken is cc7b13ffcd2ddd51

Because the two tokens are different - binding redirects does not work - or maybe I am missing something. Does anyone have a workaround for this?

The whole solution is in VS2019 and I have the latest Win10 SDK installed 10.0.18362.1.

Thank you in advance.

EDIT: I forgot to mention, I have a repro on GitHub


Viewing all articles
Browse latest Browse all 3067

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>