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

dotnet list package should warn when restore is not current #13703

Open
zivkan opened this issue Aug 13, 2024 · 1 comment
Open

dotnet list package should warn when restore is not current #13703

zivkan opened this issue Aug 13, 2024 · 1 comment
Assignees

Comments

@zivkan
Copy link
Member

zivkan commented Aug 13, 2024

NuGet Product(s) Involved

dotnet.exe

The Elevator Pitch

dotnet list package gets "actual" package usage from NuGet's assets file, which is created on restore. Which means that if a customer restores a project, then edits the project to change a package version, or add/remove a package reference, then runs dotnet list package without restoring, it will show incorrect information, and the customer will not know why.

dotnet list package should show a message when the project restore isn't up-to-date

Additional Context and Details

dotnet list package already loads the project file via MSBuild APIs (hence why it only works with SDK style projects that the dotnet CLI can build/evaluate), meaning we already have the data to do a restore no-op check.

@zivkan zivkan added Priority:1 High priority issues that must be resolved in the current sprint. Type:Feature Product:dotnet.exe Functionality:ListPackage dotnet.exe list package labels Aug 13, 2024
@zivkan zivkan self-assigned this Aug 13, 2024
@jebriede jebriede added Priority:2 Issues for the current backlog. and removed Priority:1 High priority issues that must be resolved in the current sprint. labels Sep 5, 2024
@jebriede
Copy link
Contributor

jebriede commented Sep 5, 2024

Adjusting priority after discussion with @zivkan

@zivkan zivkan removed their assignment Oct 7, 2024
@Nigusu-Allehu Nigusu-Allehu self-assigned this Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants