Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, September 2, 2014 9:55 PM
I am getting the error (title of this question) when attempting to apply an update to the Visual Studio Gallery. It doesn't matter whether I let VS2012 see that there is an update and prompt me, or if I manually fire the update process (Tools --> Extensions and Updates) the error is the same. I can't figure out what path it's looking for (where in the options there might be an incomplete path). Can anyone point me in the right direction?
Here is the contents of the log file:
9/2/2014 2:43:35 PM - Microsoft VSIX Installer
9/2/2014 2:43:35 PM -
9/2/2014 2:43:36 PM - Initializing Install...
9/2/2014 2:43:36 PM - Extension Details...
9/2/2014 2:43:36 PM - Identifier : NuPackToolsVsix.Microsoft.67e54e40-0ae3-42c5-a949-fddf5739e7a5
9/2/2014 2:43:36 PM - Name : NuGet Package Manager
9/2/2014 2:43:36 PM - Author : Microsoft Corporation
9/2/2014 2:43:36 PM - Version : 2.8.50313.31
9/2/2014 2:43:36 PM - Description : A collection of tools to automate the process of downloading, installing, upgrading, configuring, and removing packages from a VS Project.
9/2/2014 2:43:36 PM - Locale : en-US
9/2/2014 2:43:36 PM - MoreInfoURL : http://docs.nuget.org/
9/2/2014 2:43:36 PM - InstalledByMSI : False
9/2/2014 2:43:36 PM - SupportedFrameworkVersionRange : [4.0,4.5]
9/2/2014 2:43:36 PM -
9/2/2014 2:43:36 PM - SignedBy : Microsoft Corporation
9/2/2014 2:43:36 PM - Certificate Info : [Subject]
CN=Microsoft Corporation, OU=MOPR, OU=OPC, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
[Issuer]
CN=Microsoft Code Signing PCA, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
[Serial Number]
33000000B2E6906F8BE7453D5B0001000000B2
[Not Before]
1/24/2013 3:33:41 PM
[Not After]
4/24/2014 3:33:41 PM
[Thumbprint]
E4EEC5DFB7F413E5A15191DA00D017F97E3A6260
9/2/2014 2:43:36 PM - Supported Products :
9/2/2014 2:43:36 PM - Microsoft.VisualStudio.Pro
9/2/2014 2:43:36 PM - Version : [10.0]
9/2/2014 2:43:36 PM - Microsoft.VisualStudio.Pro
9/2/2014 2:43:36 PM - Version : [11.0]
9/2/2014 2:43:36 PM - Microsoft.VisualStudio.IntegratedShell
9/2/2014 2:43:36 PM - Version : [10.0]
9/2/2014 2:43:36 PM - Microsoft.VisualStudio.IntegratedShell
9/2/2014 2:43:36 PM - Version : [11.0]
9/2/2014 2:43:36 PM - Microsoft.VisualStudio.VWDExpress
9/2/2014 2:43:36 PM - Version : [10.0]
9/2/2014 2:43:36 PM - Microsoft.VisualStudio.VWDExpress
9/2/2014 2:43:36 PM - Version : [11.0]
9/2/2014 2:43:36 PM - Microsoft.VisualStudio.VPDExpress
9/2/2014 2:43:36 PM - Version : [11.0]
9/2/2014 2:43:36 PM - Microsoft.VisualStudio.VSWinExpress
9/2/2014 2:43:36 PM - Version : [11.0]
9/2/2014 2:43:36 PM - Microsoft.VisualStudio.VSWinDesktopExpress
9/2/2014 2:43:36 PM - Version : [11.0]
9/2/2014 2:43:36 PM -
9/2/2014 2:43:36 PM - References :
9/2/2014 2:43:36 PM -
9/2/2014 2:43:36 PM - System.IO.DirectoryNotFoundException: The system cannot find the path specified. (Exception from HRESULT: 0x80070003)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at Microsoft.VisualStudio.Settings.ExternalSettingsManager.GetScopePaths(String applicationPath, String suffixOrName, String vsVersion, Boolean isLogged, Boolean isForIsolatedApplication)
at Microsoft.VisualStudio.Settings.ExternalSettingsManager.CreateForApplication(String applicationPath)
at VSIXInstaller.App.GetExtensionManager(SupportedVSSKU sku)
at VSIXInstaller.App.GetExtensionManagerForApplicableSKU(SupportedVSSKU supportedSKU, IInstallableExtension installableExtension, List`1 applicableSKUs)
at VSIXInstaller.App.InitializeInstall()
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
Thank you!
All replies (3)
Thursday, September 4, 2014 2:31 AM ✅Answered
Hi John,
I'm not clear what you're asking. The screen clip and the text of my question show that I am using VS2012 and am trying to update the Nuget Package Manager (NPM).
I mean that when we click ‘Update’ button to download and install the NuGet Package Manager update, all VS products on your machine will be listed and we can select one or multiple VS to install the update during installation.
Since you got the same issue when you install NuGet Package Manager from Visual Studio Gallery, moreover the log did not report what path was not found, I advise you to post your issue in CodePlex as NuGet Package Manager said: http://nuget.codeplex.com/workitem/list/basic You can get better solution and support there.
Another suggestion is that you can consider re-installing VS which will install NuGet Package Manager automatically then upgrade the NuGet Package Manager. Maybe the issue is on VS environment.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.
Wednesday, September 3, 2014 7:28 AM
Hi John,
Which Visual Studio product did you select to apply this Nuget update?
Please make sure the selected Visual Studio product is installed well on your machine and this package can support it.
In addition, you can uninstall current NuGet Package Manager and then install 2.8.50313.31 version directly from here: http://visualstudiogallery.msdn.microsoft.com/27077b70-9dad-4c64-adcf-c7cf6bc9970c to check whether the installation can success.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.
Wednesday, September 3, 2014 3:39 PM
Thank you, Crystal!
I'm not clear what you're asking. The screen clip and the text of my question show that I am using VS2012 and am trying to update the Nuget Package Manager (NPM).
I tried uninstalling and reinstalling the NPM, but I get the exact same error when I do the install. Consequently, I now do not have NPM installed and have no way to get it installed until I solve this problem.
Additionally, while I understand uninstalling and reinstalling components can sometimes be an expedient solution, it is a brute-force solution to a problem that is almost certainly solvable by correcting a configuration setting.
My real, underlying question should actually be directed at the development team for the NPM: Why doesn't the log file tell me which path it was looking for, that turned out to be incorrect?
If I knew what path setting to correct, I could solve this problem by typing a few characters instead of spending a half-hour trying to figure out how to re-install a package that was installed automagically when I originally installed VS2012.
John