Skip to content

Commit 2f87683

Browse files
authored
Update troubleshooting steps for NuGet package restore (#3527)
1 parent c6340da commit 2f87683

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/consume-packages/Package-restore-troubleshooting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ You can also edit these settings directly in the applicable `nuget.config` file
109109
110110
## Other potential conditions
111111

112-
- You may encounter build errors due to missing files, with a message saying to use NuGet restore to download them. However, running a restore might say, "All packages are already installed and there is nothing to restore." In this case, delete the `packages` folder (when using `packages.config`) or the `obj/project.assets.json` file (when using PackageReference) and run restore again. If the error still persists, use `nuget locals all -clear` or `dotnet nuget locals all --clear` from the command line to clear the *global-packages* and cache folders as described on [Managing the global packages and cache folders](managing-the-global-packages-and-cache-folders.md).
112+
- You may encounter build errors due to missing files, with a message saying to use NuGet restore to download them. However, running a restore might say, "All packages are already installed and there is nothing to restore." In this case, delete the `packages` folder (when using `packages.config`) or the `obj/project.assets.json` file (when using PackageReference) and run restore again.
113113

114114
- When obtaining a project from source control, your project folders may be set to read-only. Change the folder permissions and try restoring packages again.
115115

0 commit comments

Comments
 (0)