Updating multiple packages (with CPM and transitive pinning) should verify the referenced versions afterwards

[keldaaas]

NuGet Product(s) Affected

Visual Studio Package Management UI

Current Behavior

With CPM and transitive pinning enabled:

Solution S contains a console app and a test project.
The console app references package A.
The test project references package B.
Package B has a dependency on package A.

ConsoleApp -> Package A
TestProject -> Package B -> Package A

Whenever one tries to update both packages at the same time with the Package Manager UI there is an error NU1109. I suppose this happens because the check for package B's dependencies doesn't take into account that package A will be updated as well. Instead it stops this process to avoid referencing different versions of package A.
At the moment the only solution is to update package A first and package B afterwards. This makes the CPM really annoying to use in solutions with a lot of dependencies.

Desired Behavior

Either take into account that a referenced transitive dependency gets updated "at the same time" or check for different versions after the updates were executed.

Additional Context

dotnet outdated updates the packages as expected.

[jgonz120]

Hello, I haven't been able to reproduce this behavior, when I try to update all packages in the PM UI it updates successfully. Can you provide an example project that reproduces this?