Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore packages in 9.0.200 takes a very long time #14147

Open
mnmr opened this issue Feb 26, 2025 · 1 comment
Open

Restore packages in 9.0.200 takes a very long time #14147

mnmr opened this issue Feb 26, 2025 · 1 comment
Assignees
Labels
Area:NewDependencyResolver Issues related to the new dependency graph resolver Functionality:Restore Priority:1 High priority issues that must be resolved in the current sprint. Type:Bug

Comments

@mnmr
Copy link

mnmr commented Feb 26, 2025

NuGet Product Used

dotnet.exe

Product Version

9.0.200

Worked before?

9.0.103

Impact

Other

Repro Steps & Context

I'm having issues with the new package restore logic, which is seemingly taking forever (aborted after 3 minutes).

I'm restoring packages using dotnet restore -f -v d <sln> but don't see anything useful in the console before the command is cancelled. It lists increasingly long restore times, with some projects completing in ms and others going on for minutes.

We're using centralized package version management and all versions are explicit (no wildcards). There's ballpark 150 projects in the solution.

Adding <RestoreUseLegacyDependencyResolver>true</RestoreUseLegacyDependencyResolver> to Directory.Build.props is a workaround. For reference, the old way of restoring packages completes in ~4s.

Verbose Logs

@jeffkl
Copy link
Contributor

jeffkl commented Feb 26, 2025

@mnmr sorry you're experiencing this issue. Fortunately, we've already fixed in and are in the process of releasing it. Its currently fixed in Visual Studio 17.13.1 and NuGet 6.13.2 and we're working on getting .NET 9.0.2xx updated. For now, as you've pointed out, setting RestoreUseLegacyDependencyResolver is a workaround.

@jeffkl jeffkl self-assigned this Feb 26, 2025
@jeffkl jeffkl added Priority:1 High priority issues that must be resolved in the current sprint. and removed Triage:Untriaged labels Feb 26, 2025
@nkolev92 nkolev92 added Functionality:Restore Area:NewDependencyResolver Issues related to the new dependency graph resolver labels Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area:NewDependencyResolver Issues related to the new dependency graph resolver Functionality:Restore Priority:1 High priority issues that must be resolved in the current sprint. Type:Bug
Projects
None yet
Development

No branches or pull requests

3 participants