Updating packages do not respect configured `DependencyVersion`

[AdmiringWorm]

What You Are Seeing?

When we are updating/upgrading packages through the package manager handler, there is a call to the UpdatePackage method.
In this method, the configured DependencyVersion is not passed along to the different walkers being used in this method, which causes dependencies to be resolved to the lowest available version.

What is Expected?

Dependencies should be resolved in the same way as we resolve direct calls to OData API in Chocolatey, to achieve this we need NuGet.Core to pass along whatever we have configured as the DependencyVersion to the walkers it uses when resolving dependencies (both locally installed, and new remote packages).

How Did You Get This To Happen? (Steps to Reproduce)

1. This was found during a debugging session when working on fixing a problem where packages that had SxS installations couldn't be installed, this was caused by it picking up the lower version than what it believed was installed.

System Details

• OS Build (In PowerShell run [System.Environment]::OSVersion.version.tostring()): Windows 10
• Windows PowerShell version (Run: $PSVersionTable): PSv5
• Chocolatey version (Run choco --version): Choco vNext

Output Log

N/A

Related Issues

chocolatey/choco#507

[pauby]

Is this linked to the chocolatey-core.extension issues we were seeing? If so, can you link to that issue from here?

[AdmiringWorm]

Not an exact link to the chocolatey-core.extension issue (or rather a problem when there are side-by-side installations available).

It was merely found while debugging that issue, fixing this wouldn't necessarily fix that problem, only partially relieve some of the pain behind it (from a user perspective).

I think there may however be a different issue that is related, that was opened on the choco repository, I'll see if I am able to dig it up again.