NuGet Package restore failed for project Miscellaneous Files: Value cannot be null or an empty string....
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?
visual-studio-2012 nuget nuget-package-restore
asked Dec 31 '13 at 15:37
Midnight Guest
7833817
add a comment |
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?
visual-studio-2012 nuget nuget-package-restore
asked Dec 31 '13 at 15:37
Midnight Guest
7833817
1
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 4 '14 at 20:47
add a comment |
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?
visual-studio-2012 nuget nuget-package-restore
asked Dec 31 '13 at 15:37
Midnight Guest
7833817
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?
visual-studio-2012 nuget nuget-package-restore
visual-studio-2012 nuget nuget-package-restore
asked Dec 31 '13 at 15:37
Midnight Guest
7833817
asked Dec 31 '13 at 15:37
Midnight Guest
7833817
edited Jan 28 '14 at 12:40
asked Dec 31 '13 at 15:37
Midnight Guest
7833817
asked Dec 31 '13 at 15:37
Midnight Guest
7833817
asked Dec 31 '13 at 15:37
Midnight Guest
7833817
7833817
1
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 4 '14 at 20:47
add a comment |
1
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 4 '14 at 20:47
1
1
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
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 4 '14 at 20:47
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 4 '14 at 20:47
add a comment |
15 Answers
15
active
oldest
votes
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!)
answered Jan 24 '14 at 10:56
st78
4,33684161
15
This worked for me had to restart, vs2013 as well.
– Anicho
Jun 9 '14 at 17:01
8
This did not work for me, vs2013 :(
– Dave Ziegler
Dec 1 '14 at 20:41
4
Did not work for me, vs2015.
– bashis
Sep 11 '15 at 15:48
2
for VS2017 just delete a hidden folder called .vs
– Tien Dinh
Aug 6 '17 at 5:05
1
The hidden .vs folder is located in the solution directory.
– JDawg
Nov 16 '17 at 18:00
|
show 3 more comments
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.
answered Mar 20 '14 at 0:23
Noctis
9,52533062
Works like a charm! thx!
– Luis Gouveia
Nov 8 at 11:06
add a comment |
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
517514
This fixed the issue for me. I only encountered the problem when building in Release.
– ctorx
May 6 '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 8 '15 at 15:57
This solved my issue.
– Ziggler
Apr 28 '16 at 18:06
add a comment |
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 3 '14 at 16:41
Eric
16527
add a comment |
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
answered Sep 9 '15 at 6:45
ToFo
5591818
This solution worked for me.
– user1451111
Mar 20 '17 at 13:58
add a comment |
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.
answered Dec 31 '13 at 23:12
user2476190
312
add a comment |
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
311
add a comment |
I fixed this by enabling auto restore on nuget packages in the solution
answered May 29 '14 at 21:10
Smitha Poluri
10124
add a comment |
Just as a brief note. I got this error by running the project on a mapped network drive i.e. T:NetworkFolderProjectSolution.sln.
Obviously the solution is simple - don't do this - copy it onto your machine. Might save someone some pain at some point.
answered Nov 21 '14 at 15:39
Crab Bucket
5,33852657
add a comment |
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
261
add a comment |
Let's check the name of packages in file packages.config. Sometime the name incorrect it occurr
answered Mar 30 '16 at 7:49
Tailmse02457
184
add a comment |
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.
answered May 12 '16 at 11:29
Eternal21
1,90312440
add a comment |
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 9:56
David J
548417
add a comment |
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,28011128
add a comment |
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!
answered Nov 20 at 13:16
IfElseTryCatch
36049
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f20859591%2fnuget-package-restore-failed-for-project-miscellaneous-files-value-cannot-be-nu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
15 Answers
15
active
oldest
votes
15 Answers
15
active
oldest
votes
active
oldest
votes
active
oldest
votes
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!)
answered Jan 24 '14 at 10:56
st78
4,33684161
15
This worked for me had to restart, vs2013 as well.
– Anicho
Jun 9 '14 at 17:01
8
This did not work for me, vs2013 :(
– Dave Ziegler
Dec 1 '14 at 20:41
4
Did not work for me, vs2015.
– bashis
Sep 11 '15 at 15:48
2
for VS2017 just delete a hidden folder called .vs
– Tien Dinh
Aug 6 '17 at 5:05
1
The hidden .vs folder is located in the solution directory.
– JDawg
Nov 16 '17 at 18:00
|
show 3 more comments
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!)
answered Jan 24 '14 at 10:56
st78
4,33684161
15
This worked for me had to restart, vs2013 as well.
– Anicho
Jun 9 '14 at 17:01
8
This did not work for me, vs2013 :(
– Dave Ziegler
Dec 1 '14 at 20:41
4
Did not work for me, vs2015.
– bashis
Sep 11 '15 at 15:48
2
for VS2017 just delete a hidden folder called .vs
– Tien Dinh
Aug 6 '17 at 5:05
1
The hidden .vs folder is located in the solution directory.
– JDawg
Nov 16 '17 at 18:00
|
show 3 more comments
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!)
answered Jan 24 '14 at 10:56
st78
4,33684161
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!)
answered Jan 24 '14 at 10:56
st78
4,33684161
edited Nov 19 '17 at 6:59
answered Jan 24 '14 at 10:56
st78
4,33684161
answered Jan 24 '14 at 10:56
st78
4,33684161
answered Jan 24 '14 at 10:56
st78
4,33684161
4,33684161
15
This worked for me had to restart, vs2013 as well.
– Anicho
Jun 9 '14 at 17:01
8
This did not work for me, vs2013 :(
– Dave Ziegler
Dec 1 '14 at 20:41
4
Did not work for me, vs2015.
– bashis
Sep 11 '15 at 15:48
2
for VS2017 just delete a hidden folder called .vs
– Tien Dinh
Aug 6 '17 at 5:05
1
The hidden .vs folder is located in the solution directory.
– JDawg
Nov 16 '17 at 18:00
|
show 3 more comments
15
This worked for me had to restart, vs2013 as well.
– Anicho
Jun 9 '14 at 17:01
8
This did not work for me, vs2013 :(
– Dave Ziegler
Dec 1 '14 at 20:41
4
Did not work for me, vs2015.
– bashis
Sep 11 '15 at 15:48
2
for VS2017 just delete a hidden folder called .vs
– Tien Dinh
Aug 6 '17 at 5:05
1
The hidden .vs folder is located in the solution directory.
– JDawg
Nov 16 '17 at 18:00
15
15
This worked for me had to restart, vs2013 as well.
– Anicho
Jun 9 '14 at 17:01
This worked for me had to restart, vs2013 as well.
– Anicho
Jun 9 '14 at 17:01
8
8
This did not work for me, vs2013 :(
– Dave Ziegler
Dec 1 '14 at 20:41
This did not work for me, vs2013 :(
– Dave Ziegler
Dec 1 '14 at 20:41
4
4
Did not work for me, vs2015.
– bashis
Sep 11 '15 at 15:48
Did not work for me, vs2015.
– bashis
Sep 11 '15 at 15:48
2
2
for VS2017 just delete a hidden folder called .vs
– Tien Dinh
Aug 6 '17 at 5:05
for VS2017 just delete a hidden folder called .vs
– Tien Dinh
Aug 6 '17 at 5:05
1
1
The hidden .vs folder is located in the solution directory.
– JDawg
Nov 16 '17 at 18:00
The hidden .vs folder is located in the solution directory.
– JDawg
Nov 16 '17 at 18:00
|
show 3 more comments
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.
answered Mar 20 '14 at 0:23
Noctis
9,52533062
Works like a charm! thx!
– Luis Gouveia
Nov 8 at 11:06
add a comment |
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.
answered Mar 20 '14 at 0:23
Noctis
9,52533062
Works like a charm! thx!
– Luis Gouveia
Nov 8 at 11:06
add a comment |
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.
answered Mar 20 '14 at 0:23
Noctis
9,52533062
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.
answered Mar 20 '14 at 0:23
Noctis
9,52533062
answered Mar 20 '14 at 0:23
Noctis
9,52533062
answered Mar 20 '14 at 0:23
Noctis
9,52533062
answered Mar 20 '14 at 0:23
Noctis
9,52533062
9,52533062
Works like a charm! thx!
– Luis Gouveia
Nov 8 at 11:06
add a comment |
Works like a charm! thx!
– Luis Gouveia
Nov 8 at 11:06
Works like a charm! thx!
– Luis Gouveia
Nov 8 at 11:06
Works like a charm! thx!
– Luis Gouveia
Nov 8 at 11:06
add a comment |
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
517514
This fixed the issue for me. I only encountered the problem when building in Release.
– ctorx
May 6 '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 8 '15 at 15:57
This solved my issue.
– Ziggler
Apr 28 '16 at 18:06
add a comment |
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
517514
This fixed the issue for me. I only encountered the problem when building in Release.
– ctorx
May 6 '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 8 '15 at 15:57
This solved my issue.
– Ziggler
Apr 28 '16 at 18:06
add a comment |
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
517514
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
517514
answered Mar 27 '14 at 11:47
InquisitorJax
517514
answered Mar 27 '14 at 11:47
InquisitorJax
517514
answered Mar 27 '14 at 11:47
InquisitorJax
517514
517514
This fixed the issue for me. I only encountered the problem when building in Release.
– ctorx
May 6 '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 8 '15 at 15:57
This solved my issue.
– Ziggler
Apr 28 '16 at 18:06
add a comment |
This fixed the issue for me. I only encountered the problem when building in Release.
– ctorx
May 6 '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 8 '15 at 15:57
This solved my issue.
– Ziggler
Apr 28 '16 at 18:06
This fixed the issue for me. I only encountered the problem when building in Release.
– ctorx
May 6 '14 at 18:58
This fixed the issue for me. I only encountered the problem when building in Release.
– ctorx
May 6 '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 8 '15 at 15:57
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 8 '15 at 15:57
This solved my issue.
– Ziggler
Apr 28 '16 at 18:06
This solved my issue.
– Ziggler
Apr 28 '16 at 18:06
add a comment |
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 3 '14 at 16:41
Eric
16527
add a comment |
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 3 '14 at 16:41
Eric
16527
add a comment |
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 3 '14 at 16:41
Eric
16527
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 3 '14 at 16:41
Eric
16527
answered Jul 3 '14 at 16:41
Eric
16527
answered Jul 3 '14 at 16:41
Eric
16527
answered Jul 3 '14 at 16:41
Eric
16527
16527
add a comment |
add a comment |
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
answered Sep 9 '15 at 6:45
ToFo
5591818
This solution worked for me.
– user1451111
Mar 20 '17 at 13:58
add a comment |
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
answered Sep 9 '15 at 6:45
ToFo
5591818
This solution worked for me.
– user1451111
Mar 20 '17 at 13:58
add a comment |
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
answered Sep 9 '15 at 6:45
ToFo
5591818
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
answered Sep 9 '15 at 6:45
ToFo
5591818
edited May 20 '16 at 10:44
answered Sep 9 '15 at 6:45
ToFo
5591818
answered Sep 9 '15 at 6:45
ToFo
5591818
answered Sep 9 '15 at 6:45
ToFo
5591818
5591818
This solution worked for me.
– user1451111
Mar 20 '17 at 13:58
add a comment |
This solution worked for me.
– user1451111
Mar 20 '17 at 13:58
This solution worked for me.
– user1451111
Mar 20 '17 at 13:58
This solution worked for me.
– user1451111
Mar 20 '17 at 13:58
add a comment |
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.
answered Dec 31 '13 at 23:12
user2476190
312
add a comment |
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.
answered Dec 31 '13 at 23:12
user2476190
312
add a comment |
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.
answered Dec 31 '13 at 23:12
user2476190
312
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.
answered Dec 31 '13 at 23:12
user2476190
312
answered Dec 31 '13 at 23:12
user2476190
312
answered Dec 31 '13 at 23:12
user2476190
312
answered Dec 31 '13 at 23:12
user2476190
312
312
add a comment |
add a comment |
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
311
add a comment |
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
311
add a comment |
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
311
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
311
answered Jan 21 '14 at 16:13
Dan Cooper
311
answered Jan 21 '14 at 16:13
Dan Cooper
311
answered Jan 21 '14 at 16:13
Dan Cooper
311
311
add a comment |
add a comment |
I fixed this by enabling auto restore on nuget packages in the solution
answered May 29 '14 at 21:10
Smitha Poluri
10124
add a comment |
I fixed this by enabling auto restore on nuget packages in the solution
answered May 29 '14 at 21:10
Smitha Poluri
10124
add a comment |
I fixed this by enabling auto restore on nuget packages in the solution
answered May 29 '14 at 21:10
Smitha Poluri
10124
I fixed this by enabling auto restore on nuget packages in the solution
answered May 29 '14 at 21:10
Smitha Poluri
10124
answered May 29 '14 at 21:10
Smitha Poluri
10124
answered May 29 '14 at 21:10
Smitha Poluri
10124
answered May 29 '14 at 21:10
Smitha Poluri
10124
10124
add a comment |
add a comment |
Just as a brief note. I got this error by running the project on a mapped network drive i.e. T:NetworkFolderProjectSolution.sln.
Obviously the solution is simple - don't do this - copy it onto your machine. Might save someone some pain at some point.
answered Nov 21 '14 at 15:39
Crab Bucket
5,33852657
add a comment |
Just as a brief note. I got this error by running the project on a mapped network drive i.e. T:NetworkFolderProjectSolution.sln.
Obviously the solution is simple - don't do this - copy it onto your machine. Might save someone some pain at some point.
answered Nov 21 '14 at 15:39
Crab Bucket
5,33852657
add a comment |
Just as a brief note. I got this error by running the project on a mapped network drive i.e. T:NetworkFolderProjectSolution.sln.
Obviously the solution is simple - don't do this - copy it onto your machine. Might save someone some pain at some point.
answered Nov 21 '14 at 15:39
Crab Bucket
5,33852657
Just as a brief note. I got this error by running the project on a mapped network drive i.e. T:NetworkFolderProjectSolution.sln.
Obviously the solution is simple - don't do this - copy it onto your machine. Might save someone some pain at some point.
answered Nov 21 '14 at 15:39
Crab Bucket
5,33852657
answered Nov 21 '14 at 15:39
Crab Bucket
5,33852657
answered Nov 21 '14 at 15:39
Crab Bucket
5,33852657
answered Nov 21 '14 at 15:39
Crab Bucket
5,33852657
5,33852657
add a comment |
add a comment |
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
261
add a comment |
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
261
add a comment |
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
261
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
261
answered Mar 31 '15 at 12:42
user2343577
261
answered Mar 31 '15 at 12:42
user2343577
261
answered Mar 31 '15 at 12:42
user2343577
261
261
add a comment |
add a comment |
Let's check the name of packages in file packages.config. Sometime the name incorrect it occurr
answered Mar 30 '16 at 7:49
Tailmse02457
184
add a comment |
Let's check the name of packages in file packages.config. Sometime the name incorrect it occurr
answered Mar 30 '16 at 7:49
Tailmse02457
184
add a comment |
Let's check the name of packages in file packages.config. Sometime the name incorrect it occurr
answered Mar 30 '16 at 7:49
Tailmse02457
184
Let's check the name of packages in file packages.config. Sometime the name incorrect it occurr
answered Mar 30 '16 at 7:49
Tailmse02457
184
answered Mar 30 '16 at 7:49
Tailmse02457
184
answered Mar 30 '16 at 7:49
Tailmse02457
184
answered Mar 30 '16 at 7:49
Tailmse02457
184
184
add a comment |
add a comment |
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.
answered May 12 '16 at 11:29
Eternal21
1,90312440
add a comment |
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.
answered May 12 '16 at 11:29
Eternal21
1,90312440
add a comment |
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.
answered May 12 '16 at 11:29
Eternal21
1,90312440
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.
answered May 12 '16 at 11:29
Eternal21
1,90312440
answered May 12 '16 at 11:29
Eternal21
1,90312440
answered May 12 '16 at 11:29
Eternal21
1,90312440
answered May 12 '16 at 11:29
Eternal21
1,90312440
1,90312440
add a comment |
add a comment |
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 9:56
David J
548417
add a comment |
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 9:56
David J
548417
add a comment |
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 9:56
David J
548417
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 9:56
David J
548417
answered May 31 '16 at 9:56
David J
548417
answered May 31 '16 at 9:56
David J
548417
answered May 31 '16 at 9:56
David J
548417
548417
add a comment |
add a comment |
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,28011128
add a comment |
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,28011128
add a comment |
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,28011128
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,28011128
answered Aug 15 '17 at 15:46
BClaydon
1,28011128
answered Aug 15 '17 at 15:46
BClaydon
1,28011128
answered Aug 15 '17 at 15:46
BClaydon
1,28011128
1,28011128
add a comment |
add a comment |
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!
answered Nov 20 at 13:16
IfElseTryCatch
36049
add a comment |
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!
answered Nov 20 at 13:16
IfElseTryCatch
36049
add a comment |
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!
answered Nov 20 at 13:16
IfElseTryCatch
36049
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!
answered Nov 20 at 13:16
IfElseTryCatch
36049
answered Nov 20 at 13:16
IfElseTryCatch
36049
answered Nov 20 at 13:16
IfElseTryCatch
36049
answered Nov 20 at 13:16
IfElseTryCatch
36049
36049
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f20859591%2fnuget-package-restore-failed-for-project-miscellaneous-files-value-cannot-be-nu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
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 4 '14 at 20:47