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:
authorDaniel Roth <daroth@microsoft.com>2019-05-06 18:35:28 +0300
committerGitHub <noreply@github.com>2019-05-06 18:35:28 +0300
commit2f1af942c8c05e1908577227899e195b47d32d98 (patch)
treed81e4042d2d8beb489d8cd9dead443dceeb1f2b1
parenta0b759d157b554896bdb11ae62593457873c0dce (diff)
Update ASP.NET Core known issues for Preview 5 (#2684)v3.0.0-preview5
-rw-r--r--release-notes/3.0/preview/3.0.0-preview-known-issues.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/release-notes/3.0/preview/3.0.0-preview-known-issues.md b/release-notes/3.0/preview/3.0.0-preview-known-issues.md
index 892abed0..ac0ff67b 100644
--- a/release-notes/3.0/preview/3.0.0-preview-known-issues.md
+++ b/release-notes/3.0/preview/3.0.0-preview-known-issues.md
@@ -25,7 +25,7 @@ This document lists known issues for **.NET Core 3.0 Preview releases** which ma
### Preview 4
-- **Server-side Blazor app fails to run on non-Windows platforms**
+- **[RESOLVED] Server-side Blazor app fails to run on non-Windows platforms**
Running a server-side Blazor app on a non-Windows platform fails with the following error:
@@ -35,7 +35,7 @@ This document lists known issues for **.NET Core 3.0 Preview releases** which ma
This will be addressed in the next preview update.
-- **A request made to a CORS-enabled endpoint wihtout an origin header fails with an HTTP 500 error.**
+- **[RESOLVED] A request made to a CORS-enabled endpoint without an origin header fails with an HTTP 500 error.**
Possible workarounds include:
@@ -59,11 +59,11 @@ This document lists known issues for **.NET Core 3.0 Preview releases** which ma
The first option would be preferred since it's not removing a check for a mis-configured application.
-- **Design-time errors in Visual Studio when using a component with child content from a component that lives in a different namespace**
+- **[RESOLVED] Design-time errors in Visual Studio when using a component with child content from a component that lives in a different namespace**
This issue will be addressed in a future preview of Visual Studio. To workaround this issue, fully qualify the name of the child component
-- **Design-time errors in Visual Studio for class libraries with Blazor components**
+- **[RESOLVED] Design-time errors in Visual Studio for class libraries with Blazor components**
This issue will be addressed in a future preview of Visual Studio. To workaround this issue add the `<AddRazorSupportForMvc>true</AddRazorSupportForMvc>` property to your project file.