NuGet Package restore failed for project Miscellaneous Files: Value cannot be null or an empty string. Parameter name: root. 0 0

Question

I have such error in vs 2012: NuGet Package restore failed for project Miscellaneous Files: Value cannot be null or an empty string. Parameter name: root. 0 0

I see that it's a bug https://nuget.codeplex.com/workitem/3780 that was fixed for version 2.8 But I can't find the 2.8 version on https://nuget.codeplex.com Is it possible to fix the error without the installation of the 2.8 version? Or how to get the 2.8?

I'm not sure on the details, but this can also happen if you attempt to use an output file name using macros, like $(SolutionDir)$(Configuration)\MyInstaller.msi I ran into this issue when trying to build a VS Installer and I assumed I could use macros in the output filename. — ryancwarren, Feb 21 '14 at 13:56
My co-worker got this with VS 2013 (plain, no Update 1 or Update 2), and he uses 2.7.x NuGet. He'll update now. — Csaba Toth, Apr 04 '14 at 20:47

st78 · Accepted Answer · 2017-11-19T06:59:56.007

153

I fixed this by deleting the visual studio solution user options file (.suo) and then restarting VS.

UPDATE: For VS 2017, you need to delete a hidden folder named .vs located in solution directory (Thanks @Tien Dinh!)

edited Nov 19 '17 at 06:59

answered Jan 24 '14 at 10:56

st78

8,028
11
49
68

I had two suo files: .suo and .v11.suo I'm using VS2012 Professional Update 3 and deleting both worked for me. I now only have the .v11.suo file present. – Fellmeister Apr 07 '15 at 01:52
2

for VS2017 just delete a hidden folder called .vs – Tien Dinh Aug 06 '17 at 05:05
1

The hidden **.vs** folder is located in the solution directory. – JDawg Nov 16 '17 at 18:00
Worked for Visual Studio 2017 Community Edition as well. Thanks (y) – Najeeb Apr 16 '18 at 12:53

score 27 · Answer 2 · answered Mar 20 '14 at 00:23

Had the same issue with VS2013 today. After running an update on installed packages (tools -> extensions and updates) (which included nuget), and installing some updates for VS2013 (windows update had some), it has gone away.

So basically, check for those updates, update, and it might solve the issue.

score 15 · Answer 3 · answered Mar 27 '14 at 11:47

15

I have VS 2013. According to the extensions manager, nuget was up to date.

Ran a manual install from the vsix site: http://visualstudiogallery.msdn.microsoft.com/4ec1526c-4a8c-4a84-b702-b21a8f5293ca

... fixed the issue.

answered Mar 27 '14 at 11:47

InquisitorJax

1,062
11
20

This fixed the issue for me. I only encountered the problem when building in Release. – ctorx May 06 '14 at 18:58
This issue appeared out of no where, literally from nonexistent to get latest on solution and boom. Same issue here that the extensions manager is borked and said it was up to date when it was not. I love Microsoft but i seriously don't understand how they're so terrible at installing software. – Chris Marisic Jun 08 '15 at 15:57

score 11 · Answer 4 · answered Jul 03 '14 at 16:41

11

A simple restart of Visual Studio should clear everything up. I had the same issue in VS2013 after upgrading Web API. It was not necessary to delete the .suo.

answered Jul 03 '14 at 16:41

Eric

185
2
7

ToFo · Answer 5 · 2016-05-20T10:44:08.607

5

I right clicked the solution and chose "Enable Nuget Package Restore". This fixed the problem.

This link from MSDN shows how:

http://blogs.msdn.com/b/dotnet/archive/2013/06/12/nuget-package-restore-issues.aspx

nuget visual-studio

edited May 20 '16 at 10:44

answered Sep 09 '15 at 06:45

ToFo

1,643
1
19
34

score 4 · Answer 6 · answered May 29 '14 at 21:10

4

I fixed this by enabling auto restore on nuget packages in the solution

answered May 29 '14 at 21:10

Smitha Poluri

121
2
4

score 3 · Answer 7 · answered Dec 31 '13 at 23:12

Not an exact answer, but best I can tell, NuGet ver. 2.8 is not available yet. I have been dealing with the same issue for sometime now (2 months). I was still able to build my solution successfully even with that error by performing the build against the main project. I am really hoping to get this issue resolved because it is a serious eyesore while working.

score 3 · Answer 8 · answered Jan 21 '14 at 16:13

3

You can get a non-release version of NuGet 2.8 here. Instructions are here: Installing a CI build. This fix the issue for me on VS2010.

answered Jan 21 '14 at 16:13

Dan Cooper

31
1

score 2 · Answer 9 · edited Aug 19 '19 at 08:12

2

I fixed this issue after clicking the "Clear All Nuget Cache(s)"

edited Aug 19 '19 at 08:12

mate00

2,727
5
26
34

answered Aug 19 '19 at 07:37

Glenox Andal

19
2

score 1 · Answer 10 · answered Nov 21 '14 at 15:39

Just as a brief note. I got this error by running the project on a mapped network drive i.e. T:\NetworkFolder\Project\Solution.sln.

Obviously the solution is simple - don't do this - copy it onto your machine. Might save someone some pain at some point.

score 1 · Answer 11 · answered Nov 20 '18 at 13:16

None of the above answers helped for me, and it was getting pretty frustrating.

What worked for me (with Visual Studio Professional 2017, version 15.8.5) was doing the following steps;

1) Tools > Options > NuGet Package Manager > Click 'Clear All NuGet Cache(s)'

Hope this helps someone!

score 0 · Answer 12 · answered Mar 31 '15 at 12:42

0

It did not work for me. I had to go to tools, extension manager... Uninstall NuGet Restart Visual Studio 2010 Download NuGet Reinstall it. Restart Visual Studio. Fixed it all!

answered Mar 31 '15 at 12:42

user2343577

36
1

score 0 · Answer 13 · answered Mar 30 '16 at 07:49

0

Let's check the name of packages in file packages.config. Sometime the name incorrect it occurr

answered Mar 30 '16 at 07:49

Tailmse02457

23
5

score 0 · Answer 14 · answered May 12 '16 at 11:29

I got this error by accidentally renaming one of the namespace id attributes inside packages.config file to something else. I was able to track this down by comparing checked in version of packages.config, with my local one. After I corrected the problem, all I had to do is close the packages.config file, rebuild, and the problem was gone.

score 0 · Answer 15 · answered May 31 '16 at 09:56

0

In Visual Studio 2015:

Go to Options->NuGet Package Manager-> Package Sources, make sure "Microsoft and .Net" is checked in the Machine-wide package list.

answered May 31 '16 at 09:56

David J

733
5
19

score 0 · Answer 16 · answered Aug 15 '17 at 15:46

0

I uninstalled and reinstalled nUnit 3.7.1 and everything started working again. I have a few nuget packages, but nunit 3.7.1 is the only one I reinstalled, I left the rest alone.

answered Aug 15 '17 at 15:46

BClaydon

1,900
2
20
34

NuGet Package restore failed for project Miscellaneous Files: Value cannot be null or an empty string. Parameter name: root. 0 0

16 Answers16

Linked