Problem with Nuget package recovery version

Question

I can’t install the package (using package recovery) due to some kind of versioning issue with Nuget. Here are the steps I took:

build project: Error: the version of the scheme "MagicalUnicorn.MvcErrorToolkit" is not compatible with the version of NuGet version 1.6.21205.9031. Update NuGet to the latest version http://go.microsoft.com/fwlink/?LinkId=213942 .

The extension manager says that version: 2.0.30619.9119.

Ok, restart VS as administrator, uninstall nuget extension manager. restart VS as administrator, search for nuget and install.

The extension manager again says that version: 2.0.30619.9119.

rebuild project: Error: The version of the scheme "MagicalUnicorn.MvcErrorToolkit" is not compatible with the version of NuGet version 1.6.21205.9031. Update NuGet to the latest version http://go.microsoft.com/fwlink/?LinkId=213942 .

So, restart VS as administrator, extension manager uninstall nuget again. This time download from http://visualstudiogallery.msdn.microsoft.com/27077b70-9dad-4c64-adcf-c7cf6bc9970c Run the installer, everything seems to be fine.

The extension manager again says that version: 2.0.30619.9119.

rebuild project: Error: The version of the scheme "MagicalUnicorn.MvcErrorToolkit" is not compatible with the version of NuGet version 1.6.21205.9031. Update NuGet to the latest version http://go.microsoft.com/fwlink/?LinkId=213942 .

Grr! Any ideas?

Answer 1

It looks like a problem in the nuget command line utility. When you enable the Nuget package repair function, it adds the .nuget folder to your solution using nuget.exe. And when you compile a project that this tool uses to download missing packages, it is not using the VS extension. Therefore, try updating this tool from the command line:

cd .nuget nuget.exe update -Self 

Screenshot of the procedure:

Answer 2

In Visual Studio 2012 it worked for me:

• Launch VS 2012 as an administrator
• Click "Tools" - "Extensions and Updates"
• In the left navigator Updates - Visual Studio Gallery
• Click Update in NuGet Package Manager.
• Install update
• Restart Visual Studio

Answer 3

None of the proposed solutions worked for me (Visual Studio 2013, Nuget Package Manager Version 2.8.5).

I had the same error, but it was said that I had version 2.5.4.

I fixed it by going to Tools> Nuget Manager Console> Nuget Package Console. This will open a command prompt window. At the top of the window was an invitation to download the missing packages for my project.

I clicked the download button and the errors were removed during the build.

Answer 4

I ran into the same problem. I solved this by selecting "Tools" in the menu "VS 2010" → "Library Package Manager" → "Package Manager Settings" → "Check for Updates". After that, I restarted VS and received a request to install the Nuget update. Once the update was installed, the Nuget package, the HTTP client in my case, was installed smoothly.

Answer 5

I ran into this problem and I checked all the answers that were on this page and in the end my problem was not solved. After a lot of searching on the Internet, I could update my nuget from the source site

http://docs.nuget.org/docs/start-here/installing-nuget

and for example for vs2010:

http://visualstudiogallery.msdn.microsoft.com/27077b70-9dad-4c64-adcf-c7cf6bc9970c

On this site, select your version of VS, and then upgrade it.

Note: before installing nuget, close all Visual Studios and open the project after installation. Thanks

Answer 6

This did not work for me completely. There is one last step that is IMPORTANT to note. After downloading the latest version of nuget, you may notice that the same error is displayed in the output window. The reason is related to the .nuget folder containing NuGet.exe, which indicates the version number.

The solution (for me and possibly for those who have not resolved your problem with the above directions) is to

• Remove the .nuget folder from your solution.

• Right-click on your web project and click on Enable Nuget Repair.

• In the above directions, a new .nuget folder should be added, this time NuGet.exe should be the newest version of the downloaded nuget.