Can't Update or Uninstall NuGet Package Manager in VS2012 - visual-studio

I am unable to update or uninstall the NuGet Package Manager for Visual Studio 2012. I've looked around to several solutions, but have not found one that works.
Running Visual Studio 2012 as the administrator...
Attempting to update the NuGet Package Manager fails, and I get this error dialog with the following at the end of the log:
2/5/2013 10:38:09 AM - Beginning to install extension to Microsoft Visual Studio Ultimate 2012...
2/5/2013 10:38:09 AM - Upgrading 'NuGet Package Manager', version 2.0.30625.9003 to version 2.2.31210.9045.
2/5/2013 10:38:10 AM - Install Error : System.IO.IOException: The process cannot access the file because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.__Error.WinIOError()
at System.IO.File.InternalMove(String sourceFileName, String destFileName, Boolean checkHost)
at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.AtomicallyDeleteFiles(IEnumerable1 filePaths, Boolean justMarkForDeletion)
at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.DeleteDiscoverableFiles(IInstalledExtension extension)
at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.UninstallInternal(IInstalledExtension extension, Boolean forceDelete)
at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.CommitInstalledAndUninstalledExtensions(IEnumerable1 installedExtensions, IEnumerable1 uninstalledExtensions, IEnumerable1 packComponentChanges)
at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.BeginInstall(IInstallableExtension installableExtension, Boolean perMachine, AsyncOperation asyncOp)
at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.InstallWorker(IInstallableExtension extension, Boolean perMachine, AsyncOperation asyncOp)
Followed by a popup telling me:
The process cannon access the file because it is being used by another process.
When I attempt to uninstall the extension first (per some solutions) I receive the same pop-up message as above, telling me the process is being used!
Steps I've made in my attempts to get this working:
I've restarted VS2012 multiple times, with and without projects loaded.
I've rebooted the computer several times and started nothing other then VS2012.
I've downloaded the NuGet installer from the web and tried to install it w/o starting VS2012 (first thing after reboot).
For step #3, I receive the same series of dialogs/errors as when attempting to update inside Visual Studio 2012.
I can't get the latest version, no matter what I try! Does anyone have another trick?
I've also noticed that NuGet is just plain not working right now. Neither the "Package Manager Console" or the "Package Manager Settings" do anything.

Source:
http://www.paraesthesia.com/archive/2013/07/30/upgrading-nuget-the-process-cannot-access-the-file-because-it.aspx
This is what helped me:
Close all instances of Visual Studio.
Go to your global Visual Studio extensions folder. NuGet doesn’t
install in your per-user folder; instead, you’ll see it in Program
Files. Something like: C:\Program Files (x86)\Microsoft Visual
Studio 11.0\Common7\IDE\Extensions
Look in that folder. You will see a lot of randomly named folders
like “sdjfksiov.djd” and so on. Most (if not all) of those are
NuGet. You’ll want to be aware of which ones are NuGet and which
ones aren’t, particularly if you have other extensions installed.
(You can tell if it's NuGet because it'll have a bunch of
NuGet.*.dll files in there. If you don't see NuGet stuff in there,
you'll want to keep it.)
Rename that Extensions folder to something like: C:\Program Files
(x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions_RENAMED
Download NuGet directly from the Visual Studio extension gallery.
Execute the downloaded NuGet.Tools.vsix file you just downloaded.
Don’t do it through Visual Studio. Just double-click the .vsix file
to install it.
NuGet should successfully install. As part of that install, it will
create the Extensions folder again, so you will once again see
C:\Program Files (x86)\Microsoft Visual Studio
11.0\Common7\IDE\Extensions
Open up your renamed extensions folder and move all of the non-NuGet
extensions into the new Extensions folder.
Now open Visual Studio. You should see the new version of NuGet
installed and working.
You can delete that renamed Extensions folder once you’ve verified
everything is working.
Download VSIX and right click unblock the file and install again

I'm using VS2010, I ended up fixing this problem by uninstalling NuGet Package Manager via the "Add Remove Programs", and then deleting this directory:
C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Microsoft Corporation\Nuget Package Manager
I could then run the NuGet.Tools.vsix thing ok.

I have VS 2013 Pro installed. What solved this problem for me was to restart into safe mode and re-install NuGet there.
You may also want to look into Adam D's post in the link below (the add-in was blocked by anti-malware software):
Can't Update or Uninstall NuGet Package Manager in VS2012

I found a solution for this issue at -
https://kc.mcafee.com/corporate/index?page=content&id=KB85636&snspd-1015&locale=en_GB&viewlocale=en_GB
Cause:
The Microsoft Visual Studio (VS) process devenv.exe must be excluded in the EEFF/FRP process exclusion registry key.
Solution:
Users with this issue must contact Intel Security Technical Support and quote this article number for assistance with adding the devenv.exe process to the correct EEFF/FRP process exclusion registry key.

Related

Is there any way of fixing this Visual studio 2015 Nuget Pacage Manager mess?

It seems I managed to completely break my Visual Studio 2015 setup by uninstalling Nuget Package Manager. I uninstalled it in order to fix its inability to update anything. Now, when I try to launch VS I get a plethora of error messages, but the most important one seems to be shown on the image below as its showing no matter what fix I attempt:
Here are the steps I took before I started seeing the above error:
I have renamed the Extensions folder found at the following path:
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE and installed Nuget Package Manager for Visual Studio 2015 from the microsoft website.
New extensions folder was created and when I tried to run the application with nothing else in it I would get the error message above once on VS launch and once on project load. When I moved old package folders from the old extensions folder I would get a lot more error messages related to the packages.
I also noticed there is an Extensions folder found at %localappdata%\Microsoft\VisualStudio\14.0, but renaming the folder to something else and just having blank folder did not help either. Also, I saw somewhere else a possible fix to an issue I thought was similar by removing contents of the folder located at: %localappdata%\Microsoft\VisualStudio\14.0\ComponentModelCache, but that didn't help either. Now with all this trying I am getting to a point where fresh install might be an only option.
UPDATE:
I guess I managed to overcome this issue by opening up this project in Visual Studio 2017. It worked without any issues, though when I originally cloned the repository from GitHub via Visual Studio 2017 it didn't work. Having said all that, I don't think its an answer I was looking for, but at least I can continue working on this project.

Why do I see a ClickOnce Dependency Error?

I have a Visio VSTO addin that has a dependency on a EULA. I am building and deploying using Visual Studio 2019 on Windows 10. This was working fine, up until the time I had to rebuild a Windows 10 dev machine.
The EULA depndency is installed under
C:\Program Files (x86)\Microsoft SDKs\ClickOnce Bootstrapper\Packages
In Visual Studio 2019 I can see and select the dependency that is deployed when I publish the plugin. However, when trying to install the ClickOnce addin from the product site I am getting the following error:
Error: Setup has detected that the file 'C:\Users\%USERNAME%\AppData\Local\Temp\VSD8AA0.tmp\cpaseulapackage\en/cpas-eula.txt' has either changed since it was initially published or may be corrupt.
In Visual Studio the 'Sign the ClickOnce manifests' and 'sign the assembly' options are checked.
I can't figure out what has changed, or caused the deployment to break. Any thoughts would be gratefully received.
Thanks and regards
Andrew
Just Refer to Alec's answer.
I made some modifications based on your situation, please try and tell me the effect.
In the following folder, you will find a product.xml file. C:\Program Files (x86)\Microsoft SDKs\ClickOnce Bootstrapper\Packages\cpaseulapackage
Open the product.xml file in Notepad (or any text editor) and under the section, you will find 1 or 2 URLs that point to the deployment package. Copy each URL into your web browser and manually download the packages.
Once the packages are downloaded, copy them to the same folder as the product.xml file (see #1 above).

How do I fix this NuGet Restart loop in Visual Studio 2017?

The NuGet prompt, "Multiple packages failed to uninstall. Restart Visual Studio to finish the process," appears repeatedly in Visual Studio 2017 no matter how many times I restart the application.
I'm selecting Tools > NuGet Package Manager > Manage NuGet Packages For Solution. Then this dialog appears.
We have a solution in VS 2017 with multiple NuGet package references which will not resolve. A colleague added these references, but when I load the solution they show up with the yellow triangles in the "bin" directory in Solution Explorer.
The missing references are for .pdb and .xml files. These problems started occurring after Visual Studio 2017 was reinstalled on my PC.
Really, I don't want to remove the references. I want them to resolve. And I want to get out of this NuGet Restart loop. Perhaps my NuGet package manager settings need to be adjusted, or I need to use the NuGet Command Prompt to fix this. Just don't know the next steps. Thanks for your help.
How do I fix this NuGet Restart loop in Visual Studio 2017?
It seems this nuget package is locked by other process, like File Explorer.
To resolve this issue, close all the Visual Studio instance first, then try to delete the \packages folder in the solution folder and delete the \bin folder manually. If you project type is .net core/.net standard, you need to clear the packages cache:
# Clear all caches (use either command)
dotnet nuget locals all --clear
nuget locals all -clear
Do not forget to restart the PC after above operations.
Check the document Clearing local folders for some more details.
Besides, do not worry those references will be removed, when you build the project, nuget will restore those package, and if find any reference missing, just execute NuGet command line in the Package Manager Console:
Update-Package -reinstall
NuGet will reinstall those packages and add references to the project.
Check the similar thread for some more details.
Hope this helps.

Visual Studio Major Issues

A few days ago now I tried to install the C++ packages for my VS2015 installation, but it wouldn't install them so I uninstalled the entirety of VS2015 and then reinstalled, but since then I've been getting tons of errors when I start the software, they are like this:
The 'Visual Studio Component Enumerator Package' package did not load correctly. The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file: 'C:Users\\AppData\Roaming\Microsoft\VisualStudio\14.0\ActivityLog.xml'.
I've attached this log at the bottom of this post.
I get around 10 of these Package errors before I can finally load into the software, but then when I try to either open an existing C# project it says "Unavailable" or if I try to start a new C++ project it says
'C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\VCWizards\default.vcxproj' cannot be opened because its project type (.vcxproj) is not supported by this version of the application. To open it, please use a version that support this type
I have tried the following to fix these issues, and every possible combination of these:
Uninstalling and reinstalling
Deleting my %appdata% in both Local and Roaming for VS 14.0
Deleting Program Files (x86)\Visual Studio 14.0
Repairing the installation
Uninstalling, cleaning registry, deleting everything I can find RE: Visual Studio and then reinstalling
devenv /setup, devenv /clearcache, devenv /uninstall /force and then reinstalling, every command line I've found anywhere.
I've been dealing with this issue for a few days and it has completely halted my development process and I'm unable to do anything with VS and it's gotten to the point where I'm extremely frustrated and not sure what to do next.
As far as I can tell there are a lot of packages missing from my installation, but Repairing my installation does not fix this. Is there a way to restore the packages?
Any assistance would be much appreciated, or is there a better forum to post this under?
Activity Log:
http://pastebin.com/pwTJQc4B

Remove NuGet Package manager from VS2013

I had an install issue with the NuGet package manager extension. I am now trying to remove it, but each time I do the remove, I come back to VS2013 PRO and it is still there (win7 sp1 box).
Is there a different way to remove it (I am getting errors whenever I try to open a project).
I ended up calling Microsoft support, and we spent about 45 minutes searching the registry for the particular version of NuGet (there was an old version installed that was not properly removed, keeping the new one from being installed).
We had to search by version id.
VS2013 does not only put things in:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions (with a random character folder name)
But also in %appdata%\Microsoft Visual Studio 12.0\Common7\IDE\Extensions as well as other places. So we had a lot of searching to do, but once we found it and removed the folder and all the old Nuget references from the registry, it was possible to continue and install the new NUGET Package Manager.
Today I found things were corrupt, (probably registry) but a REPAIR (From the install) was able to fix the problems

Resources