diff options
| author | Noah Gilson <noahgilson@microsoft.com> | 2022-11-09 23:13:25 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-11-09 23:13:25 +0300 |
| commit | eb080b31381abc18a9ae31bd43eb959153764eeb (patch) | |
| tree | 624f0e8386e84e0127ac5d78bb093841a116b305 | |
| parent | 5daa13e8bda85561c3458aa5c256a43840000675 (diff) | |
Document .NET 7 Preview Workloads Breaking Builds
See context here: https://github.com/dotnet/sdk/issues/28947
| -rw-r--r-- | release-notes/7.0/known-issues.md | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/release-notes/7.0/known-issues.md b/release-notes/7.0/known-issues.md index 5181d0e3..4e665e71 100644 --- a/release-notes/7.0/known-issues.md +++ b/release-notes/7.0/known-issues.md @@ -98,6 +98,15 @@ More information and workaround can be found at https://github.com/dotnet/runtim ## .NET SDK +### [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. + +**Workarounds** +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. + ### [RC1] dotnet restore --interactive not working for authenticated feeds The --interactive flag is not working with any dotnet.exe command in RC1. https://github.com/dotnet/sdk/issues/27597 |