Add WebApplication config reload to known issues

dotnet · Oct 11, 2021 · 1594dd5 · 1594dd5
1 parent 7cd0867
commit 1594dd5
Showing 1 changed file with 24 additions and 4 deletions.
diff --git a/release-notes/6.0/known-issues.md b/release-notes/6.0/known-issues.md
@@ -139,19 +139,19 @@ If using the `BuildServiceProvider` container directly, `ValidateOnBuild` is not
 
 ## ASP.NET Core
 
-**Running Blazor WebAssembly using IIS Express in Development**
+### 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.
 
-**Incremental builds in VS not working for apps with Razor views**
+### 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**
+### 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).
 
@@ -161,8 +161,28 @@ Issue is tracked by https://github.com/dotnet/aspnetcore/issues/33634 and will b
 
 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**
+### 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.
+
+### 
+
+There is a regression between RC1 and RC2 preventing 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`.
+
+To make configuration reloadable, you can manually add a chained configuration source as follows.
+
+```C#
+var builder = WebApplication.CreateBuilder(args);
+
+using var chainedConfiguration = new ConfigurationManager();
+chainedConfiguration.SetBasePath(builder.Environment.ContentRootPath);
+chainedConfiguration.AddJsonFile("appsettings.json", optional: true, reloadOnChange: true);
+builder.Configuration.AddConfiguration(chainedConfiguration, shouldDisposeConfiguration: false);
+
+var app = builder.Build();
+// ...
+```
+
+Issue is tracked by https://github.com/dotnet/aspnetcore/issues/37046 and will be fixed in .NET 6 RTM.