NuGet features should light up for projects that have the capability; "PackageReferences" #9957
Assignees
Labels
Functionality:Restore
Priority:2
Issues for the current backlog.
Product:VS.Client
Type:DCR
Design Change Request
Comments
This was referenced Aug 31, 2020
davkean
added a commit
to davkean/NuGet.Client
that referenced
this issue
Aug 31, 2020
nkolev92
added
Functionality:Restore
Priority:2
donnie-msft
assigned donnie-msft and nugetlurker and unassigned nugetlurker and donnie-msft
nkolev92
pushed a commit
to NuGet/NuGet.Client
that referenced
this issue
Sep 8, 2020
heng-liu
pushed a commit
to NuGet/NuGet.Client
that referenced
this issue
Sep 8, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a superset of #9358.
As part of dotnet/project-system#2491, we're adding general purpose PackageReference support to the Common Project System (CPS). Project types will opt into this feature by making sure they are marked with the "PackageReferences" capability.
Currently NuGet has a hard-coded set of project types which breaks the goal of having a project type just opt into this. NuGet can continue to consult the
SupportedProjectType.IsSupportedfor existing project types, but if that fails, fall back to doing ahierarchy.IsCapabilityMatch("PackageReferences")for projects that fail that test.The text was updated successfully, but these errors were encountered: