search

NuGet / Home

Repo for NuGet Client issues
Other
1.5k stars 253 forks source link

[Bug Bash] “Blocked by package.config” show in the “version” list of “Consolidate” tab after installing different package versions with PackageReference format into multiple projects in a solution #10526

Open v-luzh opened 3 years ago

v-luzh commented 3 years ago

Details about Problem

NuGet version: NuGet Client Dev\5.10.0.7096 VS Version: Main\31002.208 OS: Windows-10-Enterprise-20h1

Repro steps and/or sample project

  1. Create a solution with multiple C# Console App (.NET Framework 4.8) projects in VS.
  2. Right-Click the solution in the Solution Explorer and select the “Mange NuGet Packages for Solution”
  3. Go to “Browse” tab, select a package (e.g. Newtonsoft.Json) and install different versions (with PackageReference format) into the different projects. (e.g. install 12.0.1 into the first project, install 12.0.2 into the second project)
  4. Go to the “Consolidate” tab, select the package installed in step3 and observe the “version” list on the right panel.

    Expected

    There is no “Blocked by package.config” in the “version” list.

    Actual

    There is a “Blocked by package.config” (and the versions under that are unclickable) in the “version” list as below screenshot. image

    Notes

  5. It doesn’t repro when installing package with “Packages.config” format in step3.
  6. It doesn’t repro on .NET Core projects.
  7. It seems not a regression since it reproes on 16.8 GA (D16.8\30705.32) and 16.9 Preview3 (D16.9\30914.41).
nkolev92 commented 3 years ago

@v-luzh

Can you please comment when you have the regression information?

I tried a quick repro with 16.9 P3 but no luck there.

v-luzh commented 3 years ago

Hi @nkolev92, I can repro it on 16.8 GA (D16.8\30705.32) and 16.9 Preview3 (D16.9\30914.41) as below. Please pay attention the bold steps above since they are the key points to repro the bug. Please click "Updates" tab and click "Consolidate" tab back again when you can't repro it at the end of step4. And I can see it in the same list of Updates tab too. image

nkolev92 commented 3 years ago

Thanks, I can repro it now.

For me the repro occurred when I unselected one of the projects (note that in the SS right now there are 2 selected). After reselecting that project and having both selected, the repro stayed.

I think they are likely the same root cause even if the steps are not 100% the same.

aortiz-msft commented 3 years ago

@v-luzh - No reports from customers on this issue, which looks to us like an edge scenario with very specific repro steps.

v-luzh commented 2 years ago

@aortiz-msft, OK, Thanks. I changed the pipeline to Icebox.

v-luzh commented 1 month ago

It still reproes on VS Main\35222.175 with implicit NuGet Client Dev\6.12.0.82.