Home Dashboard Directory Help
Search

Package Manager Console DropdownList is empty by Amhed


Status: 

Closed
 as Fixed Help for as Fixed


2
0
Sign in
to vote
Type: Bug
ID: 758670
Opened: 8/19/2012 2:06:03 PM
Access Restriction: Public
0
Workaround(s)
view
2
User(s) can reproduce this bug

Description

Just did a fresh install of Windows 8 and Visual Studio 2012 Ultimate 2012. When i tried to use the package manager it would always throw an error, so I uninstalled NuGet and re-installed it from the "Extensions and Updates" option.

After installing everything works fine except that the dropdown lists for "Package Source" and "Default Project" are always empty
Details
Sign in to post a comment.
Posted by Microsoft on 9/19/2012 at 6:05 PM
Hello Ahmed,

I have seen this issue reported by other users as well, and it's a bug in NuGet that should be fixed in the current version.

Customers who had previously installed NuGet on their machines occasionally don't get the updated NuGet applied correctly during installation of VS 2012. To get the updated NuGet that fixes this bug, you should go into the Extensions and Updates dialog and update your NuGet extension.

Hopefully, this resolves the issue. Let me know if it does not.

Sincerely,
Clay Compton
Software Design Engineer in Test
Azure Application Platform and Tools Team
Posted by Andrew Newton_ on 9/2/2012 at 8:10 PM
I have the same issue but with Windows 7.

I have VS2010 still installed (with package manager), when I installed VS2012 I did not appear to have package manager installed in VS2012. So I went though extension manager and installed it. Everything works except for these drop downs being empty.
Posted by DBITL on 8/22/2012 at 4:02 AM
Issue occurs also on W7 Prof SP1, VS2012 Premium with fresh install of NuGet
Posted by Microsoft on 8/21/2012 at 1:29 AM
Thanks for your update. We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Amhed on 8/20/2012 at 8:25 AM
Just submitted the file with logs. Regards
Posted by Microsoft on 8/20/2012 at 2:20 AM
Thanks for reporting the issue. In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

It may help if you provide us with:
a setup log file

You can get the log files with the following steps:
1) Download collect.exe from the link below. <http://go.microsoft.com/?LinkId=8967043>
2) You may choose to save the tool for later use, or to run directly.
3) The utility creates a compressed cabinet of all the VS and .NET logs to %TEMP%\vslogs.cab.

You can get more details about how to get the log files here:
http://blogs.msdn.com/heaths/archive/2008/05/09/visual-studio-and-net-log-collection-utility.aspx

Thanks again for your efforts and we look forward to hearing from you.
Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 8/19/2012 at 2:55 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
vslogs.cab (restricted) 8/20/2012 -