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

list only packages that are compatible #318

Closed
emgarten opened this issue Mar 31, 2015 · 5 comments
Closed

list only packages that are compatible #318

emgarten opened this issue Mar 31, 2015 · 5 comments
Labels
Functionality:SDK The NuGet client packages published to nuget.org Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Resolution:Duplicate This issue appears to be a Duplicate of another issue Type:DCR Design Change Request
Milestone

Comments

@emgarten
Copy link
Member

It would be cool to have an API that lets me list only those packages that are compatible with the framework version of my current project. So for example if my current project targets .NET 2.0 and a package only has content for .NET 4.0 (\net40 is present but \net20 is not) it should not be listed in the first place.

As a bonus it would be great that if an earlier version of this package exists that does support my current target framework it should be possible to list it instead.

As the amount of packages grows, it becomes harder and harder to find to right package, especially when working with legacy code.

This is a similar issue: http://stackoverflow.com/questions/22568725/is-there-a-way-to-specify-net-framework-version-argument-while-using-install-pa

@emgarten emgarten added Functionality:SDK The NuGet client packages published to nuget.org Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Type:DCR Design Change Request labels Mar 31, 2015
@davidfowl
Copy link
Member

Server side? Noooooooooooooooo

@csharpfritz
Copy link
Contributor

I think this has to be on our radar. If you're targeting a core framework,
you won't want to be presented with a collection of packages that don't
support it.

Jeff

On Wed, Apr 1, 2015 at 7:20 AM, David Fowler notifications@github.com
wrote:

Server side? Noooooooooooooooo


Reply to this email directly or view it on GitHub
#318 (comment).

@emgarten
Copy link
Member Author

emgarten commented Apr 1, 2015

This link isn't showing up, but this was copied from a customer bug in another repo.

@yishaigalatzer
Copy link

@davidfowl please talk with @coolcsh

This is to support both the client and the server.

@yishaigalatzer yishaigalatzer added this to the 3.1.0-Beta milestone Apr 14, 2015
@yishaigalatzer yishaigalatzer modified the milestones: 3.5 Beta, 3.3.0 Nov 25, 2015
@yishaigalatzer yishaigalatzer modified the milestones: 3.5 Beta, 3.5 RC Apr 8, 2016
@nkolev92 nkolev92 added the Resolution:Duplicate This issue appears to be a Duplicate of another issue label Sep 18, 2017
@nkolev92
Copy link
Member

Dup of #4071
Closing this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Functionality:SDK The NuGet client packages published to nuget.org Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Resolution:Duplicate This issue appears to be a Duplicate of another issue Type:DCR Design Change Request
Projects
None yet
Development

No branches or pull requests

5 participants