Closed ocallesp closed 2 days ago
If you are referring to this test, I was not able to reproduce the issue. Have you tried rebuilding the project and then running the test?
@Nigusu-Allehu the report does not say that the test fails to execute. Test Explorer calls NuGet's GetInstalledPackagesAsync API, and items returned from that API have a null value for InstallPath.
In this case, all of the identifiers returned in the warning message are projects in the solution, not packages downloaded and extracted to the packages directory.
I think it's questionable if GetInstalledPackagesAsync
should return projects. It will, however, be a breaking change, since the API has been returning projects for years now. We have no way of knowing if anyone using the API has taken a dependency on knowing the (transitive) project references via NuGet.
This issue has been automatically marked as stale because we have not received a response in 14 days. It will be closed if no further activity occurs within another 14 days of this comment.
NuGet Product Used
NuGet SDK, Other/NA
Product Version
17.10.5
Worked before?
Yes
Impact
It's more difficult to complete my work
Repro Steps & Context
Test Explorer in Visual Studio 2022 is having pretty bad performance due to an issue in INuGetProjectService.GetInstalledPackagesAsync() returning result.Packages with empty InstallPath
Repro:
Verbose Logs
No response