Assets file project assets json not found Run a NuGet package restore

Question

I m trying to use nopCommerce Which is written in  NET Core  but when I want to run the project I face 52 Errors telling me Run a nuget package restore      Assets file   obj project assets json  not found  Run a NuGet package restore to generate this file   Nop Web MVC Testsote   when I use the right click on the solution and selecting Restore Nuget Packages I get this message        All packages are already installed and there is nothing to restore    but those 52 Errors are still there and in Tools -  NuGet Package Manager -  Manage NuGet Packages for Solution  there is nothing installed on the solution also I Recently updated my VS2017 to 15 5 4

User · Answer

Try this  It worked for me     Run VS as Administrator Manual update NuGet to most recent version Delete all bin and obj files in the project  Restart VS Recompile

User · Answer

For me it turned out to be a nuget source credentials problem  I had recently changed my password for accessing a nexus server and visual studio was still using the old password when trying to access a nuget on that server through the windows credential manager  To fix it  I had to delete the entry for those outdated credentials in the credential manager and after  when I did a nuget restore  it prompted me for a password letting me enter the new password  which got saved in the credential manager again  You can access the credential manager from the cmd line using CmdKey exe

User · Answer

When using VSTS  check your global json file   I had entered the sdk version as just  2 2  which caused a parse error  but not when building locally    Adding the full version   2 2 104  solved the problem

User · Answer

It was mentioned earlier but I just wanted to re-emphasize the importance of not have space anywhere in your pathing   This is what was getting me   You ve been warned

User · Answer

I got the error when I created a lambda in dot net core in VS2017  What worked for me was to unload the project and load it back

User · Answer

Very weird experience I have encountered   I had cloned with GIT bash and GIT cmd-Line earlier  I encountered the above issues   Later  I cloned with Tortoise-GIT and everything worked as expected   May be this is a crazy answer  but trying with this once may save your time

User · Answer

I lost several hours on this error in Azure DevOps when I set the  Visual Studio Build  task in a build pipeline to build an individual project in my solution  rather than the whole solution    Doing that means that DevOps either doesn t build any  or possibly some  I m not sure which  of the projects referenced by the project you ve targeted for the build  and therefore those projects won t have their project json asset files generated  which then causes this issue   The solution for me was to swap from using the VS Build task to the MSBuild task   Using the MSBuild task for an individual project correctly builds any projects referenced by the project you re building and eliminates this error

User · Answer

run your VS as administrator after that in package manager console run dotnet restore

User · Answer

For me when i did - dotnet restore still error was occurring  I went to  1  Tool - gt  NuGet Package Maneger - gt  Package Manager settings - gt  click on  quot Clear on Nuget Catche s  quot  2 dotnet restore  resolved issues

User · Answer

Seen this after adding a WinForms Core 3 1 project  from project templates  on VS-2019 vs 16 4 0 and trying to run it out of the box  Clean or Rebuild the entire solution did not work   I just reloaded my solution   that is File Close Solution and then reopening it and rebuilding it solved the problem

User · Answer

little late to the answer but seems this will add value  Looking at the error - it seems to occur in CI CD pipeline   Just running  dotnet build  will be sufficient enough       dotnet build   dotnet build runs the  restore  by default

User · Answer

In my case I had a problem with the Available Package Sources  I had move the local nuget repository folder to a new path but I did not update it in the Nuget Available Package Sources  When I ve correct the path issue  update it in the Available Package Sources and after that everything  nuget restor  etc  was working fine

User · Answer

Solved by adding  t Restore Build to MSBuild Arguments

User · Answer

In case when  dotnet restore  not works  following steps may help    Visual Studio    Tools    Options    Nuget Manager    Package Sources Unchecked any third party package sources  Rebuild solution

User · Answer

If this error occurs as part of a build in Azure DevOps  TFS  and your build already has a NuGet restore task  this error may indicate the NuGet restore task was not able to restore all packages  especially if you use a custom package source  such as an internal NuGet server   Adding  t Restore Build to the MSBuild Arguments seems to be one way to resolve the error  but this asks MSBuild to perform an additional NuGet restore operation  I believe this succeeds because MSBuild uses the custom package source configured in Visual Studio  A preferable solution is to fix the NuGet restore task   To configure a custom package source for the NuGet restore task    Create a NuGet config file that lists all of the package sources  Microsoft Visual Studio Offline Packages  nuget org  and your custom package source  and add it to source control  In the Nuget restore task under Feeds to use  select the option Feeds in my NuGet config  Provide the path to NuGet config  Remove the  t Restore Build option from the MSBuild task    Additional information is available here

User · Answer

If  mostafa-bouzari suggestion doesn t help  check carefully in  Error list  or  Output  windows for errors why NuGet cannot restore  e g  because of net problem if you re behind proxy

User · Answer

You can go for   Tools   NuGet Package Manager   Package Manager Console  And then Run   dotnet restore

User · Answer

Another one  if by any chance you re using Dropbox  check for Conflicted in file names  do a search in your repo and delete all those conflicted files   This may have happened if you have moved the files around

User · Answer

Cause of this defect  you have to remove the injected Nuget in file explorer  Solution  Once you remove that Nuget in your system  then remove from following location  select Tool  Options  NuGet Package Manager   Package Sources then uncheck Microsoft Visual Studio Offline Packages Option

User · Answer

In my case the error was the GIT repository  It had spaces in the name  making my project unable to restore   If this is your issue  just rename the GIT repository when you clone  git clone http   Your 20Project 20With 20Spaces newprojectname

User · Answer

To fix this error from Tools   NuGet Package Manager   Package Manager Console simply run   dotnet restore   The error occurs because the dotnet cli does not create the all of the required files initially  Doing dotnet restore adds the required files

User · Answer

Select Tools   NuGet Package Manager   Package Manager Console   And then Run   dotnet restore  lt project or solution name gt

User · Answer

In visual studio 2017 please do following steps   1  select Tool  Options  NuGet Package Manager   Package Sources then uncheck Microsoft Visual Studio Offline Packages Option    2  now open Tool  NuGet Package Maneger  Package Manager Console  3  execute command in PM dotnet restore   Hope its working

User · Answer

If simply restoring NuGet packages does not work make sure in Tools -  Options -  NuGet Package Manager -  General under Package Restore that the  Allow NuGet to download missing packages  is checked   Then Restore NuGet Packages again OR just REBUILD after deleting obj and bin folders

User · Answer

Nothing above worked for me  But simply deleting all  bin  and  obj  folders did the trick

User · Answer

This problem happening when your build tool is not set to do restore on projects set to use PackageReference vs packages config and mostly affect Net Core and Netstandard new style projects    When you open Visual Studio and build  it resolves this for you  But if you use automation  CLI tools  you see this issue   Many solutions are offered here  But all you need to remember  you need to force restore  In some instances you use dotnet restore before build  If you build using MsBuild just add  t Restore switch to your command   Bottom line  you need to see why restoring can t be activated  Either bad nuget source or missing restore action  or outdated nuget exe  or all of the above

User · Answer

Closing and re-opening Visual Studio solved this issue for me  once I had made sure the NuGet packages had been restored as per other answers posted here  Edit  Sometimes just trying to build again fixes the problem

User · Answer

This worked for me  added this package source    Microsoft and  net   https   www nuget org api v2 curated-feeds microsoftdotnet  then run  dotnet restore  in the console

User · Answer

To those with the same issue as me in Azure DevOps   VSTS environment encountering a similar message   C  Program Files dotnet sdk 2 2 104 Sdks Microsoft NET Sdk targets Microsoft PackageDependencyResolution targets 208 5   Error NETSDK1004  Assets file      obj project assets json  not found  Run a NuGet package restore to generate this file  Add  t Restore to your MSBuild Arguments in Build Solution

User · Answer

For me I upgraded NuGet exe from 3 4 to 4 9 because 3 4 doesn t understand how to restore packages for  NET Core   For details please see dotnet restore vs  nuget restore with teamcity

User · Answer

You will get required packages from  quot https   api nuget org v3 index json quot   Add this in Package Resources  Also make sure other packages are unchecked for time being  And Click Restore Nuget Package on Solution Explorer

[nuget] Assets file project.assets.json not found. Run a NuGet package restore

Examples related to nuget

Examples related to visual-studio-2017

Examples related to .net-core

Examples related to nuget-package-restore