Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency paths display incorrect version ranges #5852

Closed
emgarten opened this issue Sep 6, 2017 · 1 comment · Fixed by NuGet/NuGet.Client#1690
Closed

Dependency paths display incorrect version ranges #5852

emgarten opened this issue Sep 6, 2017 · 1 comment · Fixed by NuGet/NuGet.Client#1690
Assignees
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

Comments

@emgarten
Copy link
Member

emgarten commented Sep 6, 2017

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

@emgarten emgarten added this to the Backlog milestone Sep 6, 2017
@emgarten emgarten self-assigned this Sep 6, 2017
@emgarten emgarten added Functionality:Restore Priority:1 High priority issues that must be resolved in the current sprint. Area:ErrorHandling warnings and errors/log messages & related error codes. labels Sep 6, 2017
@emgarten emgarten modified the milestones: 4.4, Backlog Sep 7, 2017
@emgarten
Copy link
Member Author

emgarten commented Sep 7, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant