From 5dead96c3d332350b4a8643c2ec58cfa498541dc Mon Sep 17 00:00:00 2001 From: Artak <34246760+mkArtakMSFT@users.noreply.github.com> Date: Tue, 9 Nov 2021 15:35:58 -0800 Subject: [PATCH] IIS Express issue was fixed --- release-notes/6.0/known-issues.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/release-notes/6.0/known-issues.md b/release-notes/6.0/known-issues.md index 0a2a80c4..a1ce1d4e 100644 --- a/release-notes/6.0/known-issues.md +++ b/release-notes/6.0/known-issues.md @@ -31,10 +31,6 @@ To fix this, edit your `PATH` environment variable to either remove the `c:\Prog ## ASP.NET Core -### Running Blazor WebAssembly using IIS Express in Development - -As of .NET 6 Preview 1, there is an ongoing issue with running Blazor WebAssembly applications using an IIS Express server during development on Visual Studio. As a workaround, we recommend using Kestrel during development. - ### SPA template issues with Individual authentication when running in development The first time SPA apps are run, the authority for the spa proxy might be incorrectly cached which results in the JWT bearer being rejected due to Invalid issuer. The workaround is to just restart the SPA app and the issue will be resolved. If restarting doesn't resolve the problem, another workaround is to specify the authority for your app in Program.cs: `builder.Services.Configure("IdentityServerJwtBearer", o => o.Authority = "https://localhost:44416");` where 44416 is the port for the spa proxy.