This issue has been moved from a ticket on Developer Community.

I recommend that the Nuget setting "Allow format selection at the first package installation" is active by default (see screenshot for more accurate "1-NugetEinstellung.png").

With us team many did not know that there is an alternative package use. We just had problems with our dot.Net-Classic projects because Nuget is spinning around. This was probably because "Packages.config" is used in part and "PackageReference" in other places. The two in combination don't really work.
In addition, the TFS wants to check in the "Packages" cache all the time (which of course was also done). There were errors when checking out).

If colleagues had seen this dialogue at the first Nuget use, this would not have happened. So the standard was simply used. Unfortunately, the standard is poorly set to be said.
-> Why? Even with a brand new solution with a WinForms-Classic project and a Dot.Net standard reference, it crashes. If the new Nuget package management is used, then it will not be used.

Therefore, I think it makes a lot of sense if this function is active by default (if you calculate the man-hours in our team come out days that were spent on troubleshooting).

PS: In the German dialogue, the cancel button is hardly visible (see appendix: "2-NugetEinstellung-Auwaehldialog.png").

Original Comments

Visual Studio Feedback System on 12/18/2019, 02:29 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Original Solutions

(no solutions)