4 ms·

I really don't understand how you're having binding redirect issues with .NET core. They're usually caused by a mixup between local packages and the GAC, which

I really don't understand how you're having binding redirect issues with .NET core. They're usually caused by a mixup between local packages and the GAC, which .NET core doesn't use. When you publish a .NET core application, you can publish as stand alone and see right there in the publish directory all the DLLs that are being used.

lazulicurio 7y ago
There's still plenty of ways reference resolution with NuGet can go wrong, even without the GAC. For example, because NuGet allows packages to import .props and .targets files you can have packages that add arbitrary references that don't match your target framework or runtime. Now you could say "oh, that's the package's fault, not NuGet's", but often the reason a package includes .props or .targets files is to work around other shortcomings in NuGet.