In NuGet/NuGet.Client#7246, I realized Test-NetCoreVSandMSBuildNoOp, which is the main way we check for no-op equivalency in VS vs CLI is not running.
It was disabled in because of #13003 in NuGet/NuGet.Client#5469 but we never enabled it back.
That was Nov 10, 2023.
Unfortunately there's been many changes in this space, including a new algorithm that have basically broken this test.
This has a massive impact, since a huge number of projects have CPM enabled and everyone .NET and above has pruning data.
Some of the changes that may have regressed it:
Related: #11231
In NuGet/NuGet.Client#7246, I realized Test-NetCoreVSandMSBuildNoOp, which is the main way we check for no-op equivalency in VS vs CLI is not running.
It was disabled in because of #13003 in NuGet/NuGet.Client#5469 but we never enabled it back.
That was
Nov 10, 2023.Unfortunately there's been many changes in this space, including a new algorithm that have basically broken this test.
This has a massive impact, since a huge number of projects have CPM enabled and everyone .NET and above has pruning data.
Some of the changes that may have regressed it:
Related: #11231