[Feature]: Show updates/issues in VS Solution Explorer for packages

[timheuer]

NuGet Product(s) Involved

Other/NA

The Elevator Pitch

When working within VS, the packages I use may have updates or may have issues (security issues, deprecations, etc) that I may want to be aware of. Right now the only way to see that is launching the Package Management UI, but it isn't a normal thing I would do if nothing is alerting me to do that.

I propose that the Packages (and thus roll-up to the dependency node) node in VS should have different states for the packages listed...some examples:

• ⚠️ Warning: you should check this out and the hover tooltip would tell you something "Packages have information"
• ⬆️ or ℹ️ Information/Upgrade: your packages have updates available
• ⛔ Error: for security check or deprecation message (tooltip would show)

Example:

Additional Context and Details

Part of this exists in VSMac already today.

Issues:

• Add NuGet Package update indicators in Solution Explorer #3292
• Update... & Update All... one click commands in Solution Explorer (Context Menu) #8956

[nkolev92]

Thanks for filling this.

Duplicate of #8956.

[timheuer]

@nkolev92 problem is the dupe explicitly says this is not in scope. So when the dupe is resolved then this will still be a request

[nkolev92]

Sure, I can reopen.

We'll likely consolidate at some point, but for now, I'll let it go through triage on its own.

[zivkan]

@timheuer I had a brief chat with @drewnoakes (from project system team) about this. He tells me that the project system's dependencies tree doesn't have the capabilities to achieve this (although it's not clear to me if it's a dotnet/project-system feature, or CPS). In any case, this is going to take cross team collaboration and scheduling of priorities to achieve. I don't know who should take the lead, but FYI given you're a VS PM.

[timheuer]

@zivkan Understood -- but gotta start somewhere who owns the customer :-)...give us the requirements 😜

[zivkan]

triage: @chgill-MSFT to talk to CPS team about scheduling work to provide extensibility for overlay icons

[JonDouglas]

I've drafted an initial spec with motivation and scenarios here:

#11838

[nkolev92]

#3292 is a related issue. I think that this issue is a superior experience to #3292 and that we should probably close that issue in favor of this one.

[nkolev92]

I'm consolidating a few issues into this one. I'm treating this as an epic (See issue body)

[clabough]

If something is vulnerable and outdated, does it show both icons? If not, which has priority? There's no guarantee that the current version has addressed the vulnerability.