Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/dotnet/core.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNoah Gilson <noahgilson@microsoft.com>2022-11-10 02:29:41 +0300
committerGitHub <noreply@github.com>2022-11-10 02:29:41 +0300
commit3e6191860734b6880fe5a4a7c756660633e6de0c (patch)
tree81585a40c466604b00726f0a8bfac881b56e2ea6
parent3ce95e13364655be23e3e8a5d4ee241e15548123 (diff)
Respond to feedback + Point to official uninstall page
-rw-r--r--release-notes/7.0/known-issues.md5
1 files changed, 2 insertions, 3 deletions
diff --git a/release-notes/7.0/known-issues.md b/release-notes/7.0/known-issues.md
index df816c68..c1ea8736 100644
--- a/release-notes/7.0/known-issues.md
+++ b/release-notes/7.0/known-issues.md
@@ -100,12 +100,11 @@ More information and workaround can be found at https://github.com/dotnet/runtim
### [7.0] Projects using certain workloads don't load, build, and or run if .NET 7 Preview SDK workloads are installed:
-If a preview 7 .NET SDK is installed, projects with workload dependencies such as `microsoft.net.workload.mono.toolchain` may fail to build, load, or run. An example of this issue is described in https://github.com/dotnet/sdk/issues/28947 and also here: https://statics.teams.cdn.office.net/evergreen-assets/safelinks/1/atp-safelinks.html.
+If a preview .NET 7 SDK is installed, projects with workload dependencies such as `microsoft.net.workload.mono.toolchain` may fail to build, load, and or run. An example of this issue is described [here](https://github.com/dotnet/sdk/issues/28947).
**Resolution**
-The best method to resolve the issue is to uninstall any .NET 7 preview SDKs. On Windows, this can be done easily with add/remove programs. Another option is to try deleting the folder `C:\Program Files\dotnet\sdk-manifests\microsoft.net.workload.mono.toolchain`. [Dotnet-core-uninstall](https://github.com/dotnet/cli-lab/releases) is another option for uninstalling the .NET 7 preview SDKs.
-Why? This happened because in the middle of preview development some workloads got renamed to have .net7.0 appended to the end, partially to support multi-targeting. We've been having discussions about how to prevent the same thing happening when folks upgrade to .NET 8. We are also considering adding `dotnet workload clean` which could fix this automatically.
+The best method to resolve the issue is to uninstall any .NET 7 preview SDKs. For detailed instructions, see [dotnet uninstall instructions](https://learn.microsoft.com/en-us/dotnet/core/install/remove-runtime-sdk-versions?pivots=os-windows). For example, on Windows, dotnet preview SDKs can be uninstalled with add/remove programs. Another option is to try deleting the folder `C:\Program Files\dotnet\sdk-manifests\microsoft.net.workload.mono.toolchain`, but this will only work for file-based installs. [Dotnet-core-uninstall](https://github.com/dotnet/cli-lab/releases) is another option for uninstalling the .NET 7 preview SDKs.
### [RC1] dotnet restore --interactive not working for authenticated feeds