Nuget console getting stuck when installing-package w/ piped package names


Nuget get stuck, the stop button is not responding and I have to close VS, when I try to install package and piping names. This seems like a regression it used to work until recently.


PM> get-package -listavailable -filter "WebActivator" | install-package
Attempting to resolve dependency 'Ninject (≥ && <'.
--> stuck, stop button doesn't respond.

this repro with many packages that have dependencies :

PM> get-package -ListAvailable | install-package
Successfully installed '51Degrees.mobi'.
Successfully added '51Degrees.mobi' to WebApplication1.
Successfully installed 'AddConsoleExtension 1.0'.
Successfully added 'AddConsoleExtension 1.0' to WebApplication1.
Attempting to resolve dependency 'WebActivator (≥ 1.3)'.

--> stuck here.

PM> get-package -ListAvailable -skip 20 | install-package
Successfully installed 'Agdur 0.6'.
Successfully installed 'AGoGo 1.0'.
Successfully added 'AGoGo 1.0' to WebApplication19.
Attempting to resolve dependency 'AGoGo (≥ 1.0)'.

--> stuck here


file attachments


Haacked wrote Jul 5, 2011 at 9:48 PM

Make sure this is not a network connectivity issue. Have you tried from a local folder?

aldion wrote Jul 6, 2011 at 1:15 AM

yes I'm getting a consistent repro (always when attempting to resolve dependency), this is also something that won't time out unlike network issues.

this repro with local share too, unzip packages.zip to c:\temp and run 'get-package -listavailable -filter "WebActivator" | install-package -source "c:\temp" '

Haacked wrote Jul 6, 2011 at 3:49 PM

Luan, can you investigate?

dotnetjunky wrote Jul 6, 2011 at 10:31 PM

I can't repro. What projects are you installing to?

aldion wrote Jul 8, 2011 at 1:08 PM

I just did "get-package -ListAvailable -filter "WebActivator" | Install-Package" on a new Empty Web Application (C#/.Net 4.0).
If you can't repro I'll try debugging it, or we can look at it next week.

dotnetjunky wrote Jul 9, 2011 at 2:01 AM

Ah, I can repro it on my home machine now. Couldn't repro it at work machine.

dotnetjunky wrote Jul 9, 2011 at 2:09 AM

Haha, a deadlock situation is happening. Bravo Fowler.

AggregateQuery.cs is waiting at line 131 on the PowerShell pipeline execution thread;


And then DataServiceQueryWrapper.cs is waiting on the worker thread when attempting to aquire a lock, at line 68:

lock (_context) {

dotnetjunky wrote Jul 9, 2011 at 2:09 AM

Assign to the rightful owner :)

dotnetjunky wrote Jul 9, 2011 at 6:07 AM

Update: This only repro if we specifically select the "NuGet official package source" in the dropdown. If we select the All source, it works fine.

Haacked wrote Aug 5, 2011 at 9:51 PM

Pranav, can you look at this one? This one is critical for 1.5

pranavkm wrote Aug 15, 2011 at 10:36 PM

Fixed in changeset cdbe103a04b5

feiling wrote Jan 6 at 11:24 PM

Fixed in changeset 2506edc18dea70dea07cf5faf1f217fa40bb4c43