[Feature]: Address all the package installation rules for package namespaces work in Packages Config style projects #11036
Labels
Area:PackageSourceMapping
Issues related to the package source mapping feature
Functionality:Restore
Priority:2
Issues for the current backlog.
Style:Packages.Config
Type:Feature
Comments
kartheekp-ms
added
Type:Feature
Functionality:Restore
Style:Packages.Config
Area:PackageSourceMapping
|
Not relevant anymore, now that fully specified is the default. Feel free to reopen this and the corresponding epic issue if you think otherwise @kartheekp-ms & @erdembayar |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
NuGet Product(s) Involved
NuGet.exe, Visual Studio Package Management UI, MSBuild.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 consideredis not addressed in NuGet/NuGet.Client#4115 PR. Hence created this follow-up issue to make sure all the package installation rules are handled as per the spec forpackages.configstyle projects.Additional Context and Details
No response
The text was updated successfully, but these errors were encountered: