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:
authorMarc Paine <marcpop@microsoft.com>2022-09-14 20:35:30 +0300
committerGitHub <noreply@github.com>2022-09-14 20:35:30 +0300
commit7d9bb4d7c56fecf4479aa26f94a510a1bfca1828 (patch)
treeb714238ebe1d19c95afffd2c2530a3d34391e90a
parent5ac41de62afbe00345f191730651c6a9826ebef9 (diff)
Remove old known issues and add --interactive (#7767)
* Update known-issues.md * Adding an additional workaround
-rw-r--r--release-notes/7.0/known-issues.md38
1 files changed, 7 insertions, 31 deletions
diff --git a/release-notes/7.0/known-issues.md b/release-notes/7.0/known-issues.md
index e6651d7b..e4c65449 100644
--- a/release-notes/7.0/known-issues.md
+++ b/release-notes/7.0/known-issues.md
@@ -54,36 +54,12 @@ More information and workaround can be found at https://github.com/dotnet/runtim
## .NET SDK
-### [Testhost.exe does not find '7.0.0-preview.6.22324.4' runtime when running tests](https://github.com/dotnet/sdk/issues/26462)
-A file-based install of the SDK, dotnet test on a .NET 7 project will look in the global location rather than the local location and be unable to find .NET 7.
+### [RC1] dotnet restore --interactive not working for authenticated feeds
-Workaround: Setting DOTNET_ROOT to point to the path to the local dotnet fixes the issue.
+The --interactive flag is not working with any dotnet.exe command in RC1. https://github.com/dotnet/sdk/issues/27597
-### Blazor issues in Visual Studio 17.4 preview 1 depending on whether you’re using .NET 7 preview installed by VS or stand-alone install of .NET 7 preview 7
-
-If your app is targeting Blazor using the .NET 7 version included in VS, you can target net6.0 but not target net7.0 and you'll see an error message 'The "ProcessFrameworkReferences" task failed unexpectedly.'
-
-Workaround:
-
-Install the standalone SDK for .NET 7.0 Preview 7.
-
-### MaxInteger[T]\(System.Collections.Generic.IEnumerable`1[T]\)' violates the constraint of type parameter 'T' exception
-
-We have discovered that AutoMapper library is impacted by a change in .NET 7 Preview 5 and this is tracked by [dotnet-sdk-7.0.100-preview.5.22257.3 MaxInteger[T]\(System.Collections.Generic.IEnumerable`1[T]\)' violates the constraint of type parameter 'T' exception · Issue #3988 · AutoMapper/AutoMapper (github.com)](https://github.com/AutoMapper/AutoMapper/issues/3988). The .NET team has submitted a PR to fix the bug in AutoMapper code and is working with AutoMapper library owners to determine options.
-
-### [Unhandled Exception in dotnet format app in .NET 7.0 Preview 5](https://github.com/dotnet/sdk/issues/25879)
-
-dotnet format app that comes with SDK has this exception:
-Unhandled exception: System.IO.FileLoadException: Could not load file or assembly 'System.Configuration.ConfigurationManager, Version=6.0.0.0
-
-Workaround:
-
-[Install dotnet-format as a global tool](https://github.com/dotnet/format#how-to-install-development-builds)
-
-`dotnet tool install -g dotnet-format --version "7.*" --add-source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet7/nuget/v3/index.json`
-
-Then, invoke the global tool using `dotnet-format` instead of through the dotnet CLI using `dotnet format`.
-
-### MAUI optional workloads not yet supported in .NET 7
-
-You can continue using 6.0.200 .NET SDK versions until .NET MAUI joins the .NET 7 release. For more information, see https://github.com/dotnet/maui/wiki/.NET-7-and-.NET-MAUI.
+**Workarounds**
+- set `DOTNET_CLI_DO_NOT_USE_MSBUILD_SERVER=1` before running `dotnet`
+- `msbuild /t:restore /p:nugetInteractive=true`
+- [package source credentials](https://docs.microsoft.com/en-us/nuget/reference/nuget-config-file#packagesourcecredentials)
+- Open the project in Visual Studio