AzureAppConfigurationRefresherProvider doesn't work with .NET 6 ConfigurationManager

[pwiens]

In .NET 6 using the new minimal builder style (don't know the name) adding app configuration middleware fails because the IConfigurationRoot in this case is a ChainedConfigurationProvider so it doesn't find any refreshers.

var builder = WebApplication.CreateBuilder(args);

builder.Configuration.AddAzureAppConfiguration(o =>
{
    o.Connect("CONNECTIONSTRING");
    o.ConfigureRefresh(r =>
    {
        r.Register("Sentinel").SetCacheExpiration(TimeSpan.FromSeconds(1));
    });
});

// Add services to the container.

builder.Services.AddAzureAppConfiguration();

builder.Services.AddControllers();
builder.Services.AddSwaggerGen(c =>
{
    c.SwaggerDoc("v1", new() { Title = "MinimalAppConfigExample", Version = "v1" });
});

var app = builder.Build();

// Configure the HTTP request pipeline.
if (app.Environment.IsDevelopment())
{
    app.UseSwagger();
    app.UseSwaggerUI(c => c.SwaggerEndpoint("/swagger/v1/swagger.json", "MinimalAppConfigExample v1"));
}

app.UseAzureAppConfiguration();
app.UseHttpsRedirection();

app.UseAuthorization();

app.MapControllers();

app.Run();

[avanigupta]

Similar to #168. The same solution could fix both issues.

[zhenlan]

@avanigupta can we open an issue against .NET and request them to open up the underlying providers in ChainedConfigurationProvider?

[avanigupta]

We already have an open issue in the .NET repo: dotnet/runtime#44486

[avanigupta]

Hi @pwiens, we found that this issue does not exist in the latest .NET 6 release. The regression was introduced in .NET 6.0.0-rc.1, but it has been fixed now. Can you try the latest bits from Release/6.0.1XX (6.0.x Runtime) and confirm that it works for you?