Context

I have an application which has a dependency graph which looks like...

1. My Application
   1. Dependency1 v1.0
      1. Microsoft.Extensions.Configuration.Abstractions v5.0
   2. Dependency2 v3.1.22
      1. Microsoft.Extensions.Configuration v3.1.22
         1. Microsoft.Extensions.Configuration.Abstractions v3.1.22

Aka, two different dependencies rely on Microsoft.Extensions.Configuration.Abstractions. All dependencies are minimum versions, and are indicated as allowing higher versions. Seemingly, both should accept v5.0.

Nuget correctly picks version 5.0 as the version of the dll it put out in the bin folder. But, at runtime, when My Application tries to use Dependency2, it throws an exception:

Could not load file or assembly 'Microsoft.Extensions.Configuration.Abstractions, Version=3.1.22.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified.

What I've tried

Installing Microsoft.Extensions.Configuration.Abstractions v5.0 explicitly

This made the dependency graph look like:

1. My Application
   1. Dependency1 v1.0
      1. Microsoft.Extensions.Configuration.Abstractions v5.0
   2. Dependency2 v3.1.22
      1. Microsoft.Extensions.Configuration v3.1.22
         1. Microsoft.Extensions.Configuration.Abstractions v3.1.22
   3. Microsoft.Extensions.Configuration.Abstractions v5.0

and otherwise changed nothing. Still get the exception.

Downgrading Dependency1 to use an older version

I had a similar issue with another dependency, and resolved that by lowering the version of the dependencies until their subdependencies' versions matched.

However, Dependency1 does not have an older version that relies on Microsoft.Extensions.Configuration.Abstractions 3.1.22, so I could not do the same on this one.

Nor can I upgrade Dependendency2 to a newer version that relies on Microsoft.Extensions.Configuration.Abstractions 5.0, because then it breaks the other one I already fixed.

Setting the DependencyVersion behavior on Dependency2 to Highest instead of Lowest

The answers on this question suggested setting the DependencyVersion behavior on Dependency2 to Highest.

I did not have the UI option described in that question, so instead I ran this command in the PackageManagerConsole

Install-Package Dependency2 -Version 3.1.22 -DependencyVersion Highest

This seemingly made no difference. It still throws the exception, but also I'm not seeing any feedback that suggests the DependencyVersion was changed for that particular dependency. I'm not sure if I missed the place to check that, or if the DependencyVersion is just not available for PackageReference projects, but I'm not sure what else to try.

I am at the limit of things I can find to try. Is there a way to tell .NET which version of Microsoft.Extensions.Configuration.Abstractions to use explicitly, for all dependencies? Or something similar to Package.config's binding redirects that let you roll old versions of packages into new versions, but for PackageReference?