Open CiciLi1 opened 10 months ago
nkolev92
commented
10 months ago I wasn't as lucky to get it to repro 80% of the time, but it did repo.
Worth noting that sometimes when I'd reload the project, the PM UI would close.
Given the scenario and the lack of repro, this will likely be a low priority issue.
zivkan
commented
10 months ago If this can be reproed while using Visual Studio's feedback tool's "record steps to reproduce result" (or just collect directly with PerfView), then the .etl.zip will contain exception stacks that will tell us which method throws the exception. Sometimes just knowing the method that throws can significantly speed up investigations.
SueSu01
commented
1 month ago It still reproes on VS Main\35222.175 + NuGet Client Dev\6.12.0.82.
NuGet Product Used
Visual Studio Package Management UI
Product Version
NuGet Client Dev\6.9.0.50
Worked before?
It can be repro on 16.11[34301.259] \17.0[33801.228] \17.8[34223.131].
Impact
It bothers me. A fix would be nice
Repro Steps & Context
Repro Steps:
Create a C# Class Library (.NET Framework) project in VS.
Right-click the solution in the Solution Explorer window and select "Manage NuGet Packages for Solution..." menu item to open the solution-level PM UI.
Right-click the project in Solution Explorer and select the "Unload Project" menu item.
Right-click the project in Solution Explorer and select the "Reload Project" menu item.
Observe the Installed/Updated/Consolidate tab in solution-level PM UI.
Expected:
There is no error in the Installed/Updated/Consolidate tab.
Actual:
An error “isEmpty” occurs in the Installed/Updated/Consolidate tab as below:
Notes:
The repro rate is 80%.
The issue also repro on .Net Core template project.
The error is described as “An internal error occurred. Please contact Microsoft Support.” on 16.11 and 17.0 branch.
Verbose Logs
No response