Clash Royale CLAN TAG

Nuget packages - the dependency crisis

Perhaps it's a bit of a hyperbole to say crisis, but there clearly is a growing problem relating to package inter-dependences which doesn't seem to have an easy fix.

For example, I raised an issue with Microsoft months ago about a circular dependency created when you want to use Microsoft.AspNetCore.SignalR with Microsoft.NET.Sdk.Functions; they both want different versions of Newtonsoft.Json - see link. I also raised an issue about not being able to use PowerShell with ASP.NET Core 2.0 which has been ongoing since March 2018 seemingly due to package dependency problems - see link. Searching various forums suggests that many people are hitting similar problems with Microsoft packages.

Question: What are people's thoughts about addressing these sorts of problems? For example, would it be possible to specify versions of package dependencies so that when loading Package A (having a dependency on Package Z version 1) with Package B (having a dependency on Package Z version 2) both versions of Package Z will be loaded into different parts of code memory with the appropriate fixups to the code from Packages A and B? Clearly this would imply that when distributing my application it would be possible to put the different DLLs for the Package Z versions into different directories. Can this be done? How?

Links

SignalR and Microsoft.NET.Sdk.Functions

Powershell Issue 4669

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.