From c1e8625cb1ba7b17ce1cc07abf16872c36320327 Mon Sep 17 00:00:00 2001 From: Sebastien Pouliot Date: Fri, 20 May 2022 10:14:07 -0400 Subject: [PATCH] docs: Fix 'dotnet tool update' argument --- doc/using-uno-check.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/using-uno-check.md b/doc/using-uno-check.md index ec0c8e2c..e2a9b7d4 100644 --- a/doc/using-uno-check.md +++ b/doc/using-uno-check.md @@ -45,7 +45,7 @@ If it finds something missing, out of date, or misconfigured, it will either off If you run into problems with uno-check, you should generally try the following: -1. Update the tool to the latest version: `dotnet tool update -g uno.check --source https://api.nuget.org/v3/index.json` +1. Update the tool to the latest version: `dotnet tool update -g uno.check --add-source https://api.nuget.org/v3/index.json` 2. Run with `uno-check --force-dotnet` to ensure the workload repair/update/install commands run regardless of if uno-check thinks the workload versions look good 3. If you have errors still, it may help to run the [Clean-Old-DotNet6-Previews.ps1](https://github.com/unoplatform/uno.check/blob/main/Clean-Old-DotNet6-Previews.ps1) script to remove old SDK Packs, templates, or otherwise old cached preview files that might be causing the problem. Try running `uno-check --force-dotnet` again after this step. 4. Finally, if you have problems, run with `--verbose` flag and capture the output and add it to a new issue.