Update experience for large solutions

[vsfeedback]

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

---

Can someone please make the upgrade process easier for nuget packages.
I tried to upgrade from the sln level with select all and upgrade.
All I got were errors saying downgrade detected on all the packages I selected.
Then I spent checking packages were downloaded and did find replace to
get all the versions correct. Then I got errors saying Microsoft.EntityFrameworkCore.Relational needed to
be installed in a bunch of projects. The list of projects is alphabetically ordered with no reference to folder, however
the list in nuget for managing at the sln lever is folder then project. So just checking off down the list does not
work. I don't know what has gone wrong on upgrading nuget from net core 3.0 to 3.1. I would love to know
if the dependency order of packages is correct. I would love to see an option at sln level to list projects in alphabetical order
but please do something. The updates come quickly and if it takes this long for simple package upgrades updating so
often is not worth it.

---

Original Comments

Visual Studio Feedback System on 12/16/2019, 01:16 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)

[nkolev92]

Related to #5761
#7284
#7318
#8256

[nkolev92]

Some ideas to consider before these features land.

PackageReference works the exact same way from visual studio and commandline. CommandLine allows you to iterate quicker.
Consider the architecture/codemap to get the project dependency graph :)