User's secrets are not used in the new templates in Net 6 RC1

[AlbertoPa]

Describe the bug

New web apps, apis and Blazor hosted applications created with the new templates do not use user's secrets set in secrets.json without manually adding:

builder.WebHost.ConfigureAppConfiguration((hostContext, builder) =>
 {
     if (hostContext.HostingEnvironment.IsDevelopment())
     {
         builder.AddUserSecrets<Program>();
     }
 });

after var builder = WebApplication.CreateBuilder(args);.

To Reproduce

Create a new web application, web api or Blazor hosted application which uses EF Core, so it requires a connection string, as an example piece of information that may be stored in secrets.json. Set a connection string in secrets.json different from the default in appsettings.json. Execute Add-Migration and Update-Database in the package manager console. The connection string from appsettings will be used rather than the one from secrets.json.

Further technical details

• ASP.NET Core version: Net 6 RC1
• Include the output of dotnet --info:

.NET SDK (reflecting any global.json):
 Version:   6.0.100-rc.1.21463.6
 Commit:    e627d556a1

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.19043
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\6.0.100-rc.1.21463.6\

• The IDE (VS / VS Code/ VS4Mac) you're running on, and its version: VS 2020 Preview 4.1 Community Edition (64 bit)

[davidfowl]

I can't reproduce this on rc1. Can you provide us with a runnable sample?

[AlbertoPa]

Hi @davidfowl,

thanks for your prompt response. The default template shows the problem if you issue, for example Update-Database or Drop-Database in the package manager console after setting two different connection strings in secrets.json and appsettings.json. After investigating more, this seems limited to database operations in the package manager console (should it be reported to the EF team?)

To give more details, the connection string is correctly set here (I replaced mine with this placeholder in secrets.json).

but the connection string in appsettings.json will be used:

My secrets.json looks like (valid string replaced with placeholder):

My appsettings.json is:

[davidfowl]

I see this is specially about the migration tools. I know what the problem is here.

[davidfowl]

Another workaround looks like this:

var builder = WebApplication.CreateBuilder(new WebApplicationOptions { Args = args, ApplicationName = typeof(Program).Assembly.GetName().FullName });

[davidfowl]

This is an issue with the logic we added to resolve the service provider from the new top level statements based applications. I'm working on a fix.

cc @bricelam @ajcvickers

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ajcvickers]

Moving this to runtime, since the fix should go in HostFactoryResolver. See #59743

Tagging subscribers to this area: @eerhardt, @maryamariyan
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Describe the bug

New web apps, apis and Blazor hosted applications created with the new templates do not use user's secrets set in secrets.json without manually adding:

builder.WebHost.ConfigureAppConfiguration((hostContext, builder) =>
 {
     if (hostContext.HostingEnvironment.IsDevelopment())
     {
         builder.AddUserSecrets<Program>();
     }
 });

after var builder = WebApplication.CreateBuilder(args);.

To Reproduce

Create a new web application, web api or Blazor hosted application which uses EF Core, so it requires a connection string, as an example piece of information that may be stored in secrets.json. Set a connection string in secrets.json different from the default in appsettings.json. Execute Add-Migration and Update-Database in the package manager console. The connection string from appsettings will be used rather than the one from secrets.json.

Further technical details

• ASP.NET Core version: Net 6 RC1
• Include the output of dotnet --info:

.NET SDK (reflecting any global.json):
 Version:   6.0.100-rc.1.21463.6
 Commit:    e627d556a1

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.19043
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\6.0.100-rc.1.21463.6\

• The IDE (VS / VS Code/ VS4Mac) you're running on, and its version: VS 2020 Preview 4.1 Community Edition (64 bit)

Author:	AlbertoPa
Assignees:	davidfowl
Labels:	untriaged, area-Extensions-Hosting
Milestone:	-