How to upgrade packages inside .Net standard library 1.3 used in Quikgraph

[Aamz93]

Can we upgrade packages inside .Net standard library 1.3 used in Quikgraph?

[KeRNeLith]

Hello @Aamz93,

Package .Net standard library 1.3 is something that is automatically added to a project targetting some old standard version. The package was made by Microsoft team and of course defines some dependencies. BTW you should be aware that packages that go into the output of an application you're compiling are the result of the application of several rules implemented by the nuget executable. Among those rules there are some that allow you to add a dependency to your project of a package being itself referenced by one of the other dependencies. Note that the nuget resolution is all about this topic meaning it try to chose the best matching package to integrate to final build considering what is requested by project.

Of course if a project need a version 1, and another a version 2, while version 1 and 2 have an API break then it might cause some runtime issues. Those issues will occur if the dependencies and you use some code that is not relying on the same state of an API. That why if a package still remains with old dependencies never updated you may get issues.

So to sum up, yes you can upgrade dependencies to packages of the standard library that will be present in the output of your build but keep in mind that you may get issues at runtime (or compile time) by doing so. It totally depends on the used API. Obviously reducing dependencies to the minimum is key to not bother with such problem! But it's not always possible.
Genrally nuget will priorize the version of a package dependency that is the nearest to the built project.

Consider following cases:

Case 1:

	use
YourProject	<=====	Standard Library
		ref package A (v1)

Then the version 1 of package A will most probably be selected

Case 2:

	use
YourProject	<=====	Standard Library
ref package A (v2)		ref package A (v1)

Then the version 2 of package A will most probably be selected (even if YourProject do not explicitly use the package A.