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

[Feature]: Address all the package installation rules for package namespaces work in PackageReference and PackageDownload scenarios. #11035

Closed
kartheekp-ms opened this issue Jul 16, 2021 · 1 comment
Assignees
Labels
Area:PackageSourceMapping Issues related to the package source mapping feature Functionality:Restore Priority:2 Issues for the current backlog. Style:PackageReference Type:Feature

Comments

@kartheekp-ms
Copy link
Contributor

kartheekp-ms commented Jul 16, 2021

NuGet Product(s) Involved

NuGet.exe, Visual Studio Package Management UI, Visual Studio Package Manager Console, MSBuild.exe, dotnet.exe

The Elevator Pitch

The package installation rules in the package namespaces spec has rule: When a package id needs to be downloaded, it is first compared against sources with namespaces. If any match, only those sources are used. If none of the namespaces match, then the sources without namespaces are considered, if any. The second half of the requirement i.e. If none of the namespaces match, then the sources without namespaces are considered is not addressed in NuGet/NuGet.Client#4149 PR. Hence created this follow-up issue to make sure all the package installation rules are handled as per the spec.

Additional Context and Details

No response

@nkolev92
Copy link
Member

nkolev92 commented Sep 3, 2021

This one is irrelevant right now, as the default is FullySpecified.

Feel free to reopen if otherwise @kartheekp-ms

@nkolev92 nkolev92 closed this as completed Sep 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area:PackageSourceMapping Issues related to the package source mapping feature Functionality:Restore Priority:2 Issues for the current backlog. Style:PackageReference Type:Feature
Projects
None yet
Development

No branches or pull requests

2 participants