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

[Question] Update NuGet package dependencies with VS2017 PackageReference #6185

Closed
alex-zyl opened this issue Nov 14, 2017 · 2 comments
Closed
Labels
Resolution:Duplicate This issue appears to be a Duplicate of another issue
Milestone

Comments

@alex-zyl
Copy link

NuGet package may reference other packages that are not up-to-date at the moment of adding to the project.
Example:

Latest Microsoft.Azure.Search 3.0.4
--> Microsoft.Rest.ClientRuntime 2.3.7
... other dependencies

Latest Microsoft.Rest.ClientRuntime --2.3.10

With packages.config all dependent packages are installed along with initial package and can be updated to latest on Update tab all at once.

With PackageReference developer has to traverse dependency graph and install desired latest dependent packages manually.
With packages that bring dozens of dependent packages (like AspNetCore or EFCore) this actions are tedious.

Is it in plans to support updating dependent packages like we currently have with packages.config?

@emgarten
Copy link
Member

Duplicate of #5887

@emgarten emgarten marked this as a duplicate of #5887 Nov 14, 2017
@alex-zyl
Copy link
Author

@emgarten
I was trying to find similar threads. That's what i was looking for. Thanks!
Closing this one

@emgarten emgarten added this to the 4.6 milestone Nov 14, 2017
@emgarten emgarten added the Resolution:Duplicate This issue appears to be a Duplicate of another issue label Nov 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution:Duplicate This issue appears to be a Duplicate of another issue
Projects
None yet
Development

No branches or pull requests

2 participants