VS 2013 Manage Packages for Solutions causes VS to hang forever


VS 2013 Manage Packages for Solutions causes VS to hang forever

file attachments


deepakverma wrote Oct 16, 2013 at 3:18 PM

Can you please share you solution for a repro?

or shar what is the structure of the solution, what all packages are installed. Where exactly does it hang, does it hang while launching the dialog?

citykid wrote Oct 16, 2013 at 4:00 PM

I cannot share the solution. It hanged in the dialog. After manually cleaning packages it now works again.

RanjiniM wrote Oct 23, 2013 at 6:58 PM

Closing the issue as the customer confirmed that things are working now.

** Closed by RanjiniM 10/23/2013 11:58AM

citykid wrote Oct 26, 2013 at 3:27 PM

Well, actually it happens again.

deepakverma wrote Oct 26, 2013 at 5:48 PM

Can you please share more details on the repro steps. How many projects are there in the solution? Which operation it hangs, were you on installed tab of the dialog? Can you share packages.config of the project for which it hangs?

citykid wrote Oct 26, 2013 at 6:11 PM

sure, below are the packages.config inside the verious projects.

the hanging only appears when i open the "manage nuget packages for solution" dialog, not for any project related nuget dialog.

when it hangs, I have to kill Visual Studio, no other cancel button reacts.

<?xml version="1.0" encoding="utf-8"?>
<package id="Newtonsoft.Json" version="5.0.7" targetFramework="net45" />
<package id="NLog" version="2.1.0" targetFramework="net45" />

<?xml version="1.0" encoding="utf-8"?>
<package id="Newtonsoft.Json" version="5.0.7" targetFramework="net45" />
<package id="NLog" version="2.1.0" targetFramework="net45" />
<package id="NLog.Config" version="2.1.0" targetFramework="net45" />
<package id="NLog.Schema" version="2.1.0" targetFramework="net45" />
<package id="NodaTime" version="1.1.1" targetFramework="net45" />
<package id="ServiceStack.Text" version="3.9.67" targetFramework="net45" />

<?xml version="1.0" encoding="utf-8"?>
<package id="BingMapsTypeScript" version="1.0.1" targetFramework="net45" />
<package id="elmah.corelibrary" version="1.2.2" targetFramework="net45" />
<package id="FontAwesome" version="3.2.1" targetFramework="net45" />
<package id="Glimpse" version="1.4.2" targetFramework="net45" />
<package id="Glimpse.AspNet" version="1.3.0" targetFramework="net45" />
<package id="Glimpse.Mvc4" version="1.3.1" targetFramework="net45" />
<package id="jasmine.TypeScript.DefinitelyTyped" version="0.1.5" targetFramework="net45" />
<package id="JasmineTest" version="1.3.1" targetFramework="net45" />
<package id="jQuery" version="2.0.2" targetFramework="net45" />
<package id="jquery.TypeScript.DefinitelyTyped" version="0.3.0" targetFramework="net45" />
<package id="jqueryui.TypeScript.DefinitelyTyped" version="0.1.4" targetFramework="net45" />
<package id="linq.TypeScript.DefinitelyTyped" version="0.0.8" targetFramework="net45" />
<package id="Microsoft.AspNet.Mvc" version="4.0.30506.0" targetFramework="net45" />
<package id="Microsoft.AspNet.Razor" version="2.0.30506.0" targetFramework="net45" />
<package id="Microsoft.AspNet.SignalR.Core" version="1.1.2" targetFramework="net45" />
<package id="Microsoft.AspNet.SignalR.JS" version="1.1.2" targetFramework="net45" />
<package id="Microsoft.AspNet.SignalR.Owin" version="1.1.2" targetFramework="net45" />
<package id="Microsoft.AspNet.SignalR.SystemWeb" version="1.1.2" targetFramework="net45" />
<package id="Microsoft.AspNet.Web.Optimization" version="1.0.0" targetFramework="net40" />
<package id="Microsoft.AspNet.WebPages" version="2.0.30506.0" targetFramework="net45" />
<package id="Microsoft.Owin.Host.SystemWeb" version="1.0.1" targetFramework="net45" />
<package id="Microsoft.Web.Infrastructure" version="" targetFramework="net40" />
<package id="Newtonsoft.Json" version="5.0.7" targetFramework="net45" />
<package id="NLog" version="2.1.0" targetFramework="net45" />
<package id="Owin" version="1.0" targetFramework="net45" />
<package id="routedebugger" version="" targetFramework="net40" />
<package id="signalr.TypeScript.DefinitelyTyped" version="0.0.9" targetFramework="net45" />
<package id="WebGrease" version="1.3.0" targetFramework="net45" />

<?xml version="1.0" encoding="utf-8"?>
<package id="Newtonsoft.Json" version="5.0.7" targetFramework="net45" />
<package id="NLog" version="2.1.0" targetFramework="net45" />
<package id="NodaTime" version="1.1.1" targetFramework="net45" />

danliu wrote Nov 4, 2013 at 6:04 PM

reactivate since the issue resurface again.

ugumba wrote Nov 5, 2013 at 11:03 AM

I've had the same issue since VS2012, and now with VS2013.
I've attached a screenshot.

deepakverma wrote Nov 8, 2013 at 6:22 PM

@citykid do you also have same issue as @ugumba (a screenshot is attached) ?
The issue is that the projects are still being loaded by VS (you can look at the solution explorer to see this)
and user launches NuGet package manager.
I feel Workaround would be to wait for all the projects to be loaded in the solution before launching package manager. Can you please confirm this workaround works for you for now?

citykid wrote Nov 8, 2013 at 7:34 PM

Just tried it again. Opening Manage NuGet Packages for Solution
  • opens the Dialog
  • opens a progress dialog box saying

    "Loading the projects is required to completed the requested action. If you click the Cancel button, project loading will continue ..."
Aside: The operating system is disturbed so much that I suddenly could not even continue writing this message. Had to kill VS to be able to continue.

So, I thought the unloaded projects appearently cause the issue, I unload projects very frequently and hardly have all loaded. Tried again, loaded all projects, no change. It hangs on loading project 1.

There are no projects in loading phase now, all are loaded and loaded completely.

Is there maybe any diagnostics that let us find which project is the "Project 1" ? Anything I can do to help?

My workaround
For me this issue is not too serious, i usually add nuget packages per project and the package manager then realizes that the package is already in the solution. The solution level manager is certainly more comfortable for this task, in particular as it helps avoiding to have different versions of a package inside a solution.

citykid wrote Nov 8, 2013 at 10:05 PM

about the screenshot: my issue looks exactly the same. in my case it stops on loading project 1.

ugumba wrote Nov 9, 2013 at 9:36 PM

The error most certainly not indicate that VS is still loading projects. The hang occurs when I try to manage packages at the solution level after working normally with the solution for hours.

When the hang occurs, no unusual amount of cpu is being used. Process monitor shows almost no file activity, at least nothing that seems related.

So to me it looks like VS and nuget have ended up in a deadlock situation.

danliu wrote Dec 3, 2013 at 10:29 PM

Are the solutions associated with SourceGear Vault? If so, we've written a blog post about this issue, with its workaround:


citykid wrote Dec 4, 2013 at 3:27 PM


danliu wrote Dec 16, 2013 at 9:40 PM

assign to Fei to take a look.

feiling wrote Dec 19, 2013 at 5:55 PM

I couldn't repro the problem. I can open the "manage packages for solution" dialog even when the solution (or its child projects) is being loaded, without any problems.

Please attach another instance of VS when the hang happens and take the dump file (see http://msdn.microsoft.com/en-us/library/d5zhxt22.aspx for instructions) and send it to us to help us investigate this problem.

ugumba wrote Dec 20, 2013 at 2:32 PM

Dump files have been sent in private to @feiling.

existent wrote Apr 18, 2014 at 6:51 AM

I have exactly same problem. When I delete the *.suo file the manager won't freeze and everything is fine. But when I reopen Visual Studio, problem is back again.

Trinition wrote Jul 17, 2014 at 7:37 PM

FYI: Using SourceGear Vault, Visual Studio 2013 Update 2, NuGet... Manage packages for solutions still hangs for me (and all of my colleagues).

danliu wrote Jul 17, 2014 at 8:21 PM

when the hang happens, can you please take a dump file and attach to the bug? It will help us diagnose the issue, thanks!

darwinairola wrote Mar 8, 2016 at 5:53 PM

I seem to be having the same problem with Visual Studio 2013, but deleting the *.suo file seems to have no impact upon the problem.