From b3c362a4544763c56a4132d030289424eb9384db Mon Sep 17 00:00:00 2001 From: Artak <34246760+mkArtakMSFT@users.noreply.github.com> Date: Tue, 9 Nov 2021 14:57:55 -0800 Subject: [PATCH 1/2] Updated ASP.NET 6.0 known issues Removed the issues which were fixed --- release-notes/6.0/known-issues.md | 58 ------------------------------- 1 file changed, 58 deletions(-) diff --git a/release-notes/6.0/known-issues.md b/release-notes/6.0/known-issues.md index a3b2729f..0a2a80c4 100644 --- a/release-notes/6.0/known-issues.md +++ b/release-notes/6.0/known-issues.md @@ -35,64 +35,6 @@ To fix this, edit your `PATH` environment variable to either remove the `c:\Prog 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. -### Incremental builds in VS not working for apps with Razor views - -As of .NET 6 Preview 3, changes to Razor views will not be updated during incremental builds. As a workaround, you can: - -- Build from the command line -- Configure VS to always call MSBuild when building projects -- Clean and build projects to pick up changes - -### JWT Bearer Handler ArgumentOutOfRangeException in UTC+X time zones - -As of .NET 6 Preview 5, when using the JWT Bearer handler in a time zone that is higher than UTC (e.g. Eastern European Time/UTC+2), you may observe an `ArgumentOutOfRangeException` if the JWT token does not contain a `nbf` value (valid from). - -Issue is tracked by https://github.com/dotnet/aspnetcore/issues/33634 and will be fixed in .NET 6 Preview 6. - -**Workaround** - -You can workaround this by always providing a non-zero and non-minimum value for the `notBefore` parameter when using System.IdentityModel.Tokens.Jwt.JwtSecurityToken, or the 'nbf' field if using another JWT library. - -### CPU at 100% when enabling HTTP/3 Preview - -When enabling HTTP/3 which is only accessible through a feature flag, you might experience Kestrel using 100% of the CPU. We recommend not enabling the feature until this is fixed. - -Issue is tracked by https://github.com/dotnet/runtime/issues/60133 and will be fixed in .NET 6 RTM. - - -**Customizing WebRootPath not supported for minimal applications** - -There is a known issue with modifying the `WebRootPath` in a minimal app using the `WebApplicationBuilder` as documented in https://github.com/dotnet/aspnetcore/issues/36999. The issue will be resolved in .NET 6 RTM. As a workaround, users can use the default `wwwroot` directory for serving static files in their applications. Alternatively, you can invoke `UseStaticFiles` with a `StaticFilesOption` containing both the provider and path. - -```csharp -app.UseStaticFiles(new StaticFileOptions -{ - ContentTypeProvider = new PhysicalFileProvider("/full/path/to/custom/wwwroot") -}); -``` -### Configuration not reloaded on changes - -A regression introduced in .NET 6 RC2 prevents configuration from being reloaded on changes when using `WebApplication.Create()` and `WebApplication.CreateBuilder()`. This includes both custom configuration sources and default configuration sources such as `appsettings.json`. - -Issue is tracked by https://github.com/dotnet/aspnetcore/issues/37046 and will be fixed in .NET 6 RTM. - -**Workaround** - -To make configuration reloadable in RC2, you can manually add a chained configuration source as follows. - -```C# -var builder = WebApplication.CreateBuilder(args); - -var chainedConfiguration = new ConfigurationBuilder() - .SetBasePath(builder.Environment.ContentRootPath) - .AddJsonFile("appsettings.json", optional: true, reloadOnChange: true) - .AddJsonFile($"appsettings.{builder.Environment.EnvironmentName}.json", optional: true, reloadOnChange: true); -builder.Configuration.AddConfiguration(chainedConfiguration.Build()); - -var app = builder.Build(); -// ... -``` - ### 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. 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 2/2] 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.