Revised proposal for Adding dotnet CLI support for projects onboarded to CPM (Take 3)

[kartheekp-ms]

Tracking issue #11858

Rendered Design Spec

Proposal for 11807

Here is what changed when compared to the initial proposal:

1. Modified spec template as per https://github.com/NuGet/Home/blob/dev/meta/template.md
2. We identified various scenarios while brainstorming edge cases that are not covered in previous pull requests.

[jeffkl]

Thanks for the hard work involved in getting this spec'd out!

[nkolev92]

Thanks for updating this!

I think the spec still suggests some scenarios are in scope, but realistically only the first 4 are.

[nkolev92]

This creates an experience gap which is the dotnet add package equivalent for this issue: #11912.

@jeffkl Do you want to use the same issue for any potential updates there or should we create a dotnet add package specific one?

[kartheekp-ms]

I guess the code path is shared for VS and dotnet.exe. Hence once we address #11912 then it would impact dotnet add package also. Please correct if my understanding is incorrect.

https://github.com/NuGet/NuGet.Client/blob/dev/src/NuGet.Core/NuGet.CommandLine.XPlat/Commands/PackageReferenceCommands/AddPackageReferenceCommandRunner.cs#L331

[nkolev92]

Not all the code is shared for that actually.
There's a lot of NuGetPackageManager usage in VS.
VS can also update multiple projects at a time.

[pragnya17]

@jeffkl @nkolev92 @kartheekp-ms I have pushed the changes we discussed at our spec review meeting. Please let me know if it all looks good!

[nkolev92]

LGTM.