Dependency paths display incorrect version ranges #5852
Labels
Area:ErrorHandling
warnings and errors/log messages & related error codes.
Functionality:Restore
Priority:1
High priority issues that must be resolved in the current sprint.
Milestone
Dependency paths for downgrade and version conflict messages with PackageReference projects display the incorrect version range for a dependency.
Expected:
The version range used in the nuspec
Actual:
The range >= {resolved version} is used
A new format that includes both the resolved version and the range might make these messages more useful. Alternatively the resolved version could be used for all packages except the conflicts which could show the range.
Related: #5463
The text was updated successfully, but these errors were encountered: