Update ASP.NET Core C# project templates to use new minimal hosting APIs in .NET 6

[DamianEdwards]

The ASP.NET Core project templates included in the SDK should be updated to use the new minimal hosting APIs introduced in .NET 6 as they represent the new idiomatic way to bootstrap (configure and start) the relevant host for the majority of scenarios.

• The CreateHostBuilder method would be removed as the patterns that were previously reliant on this are no longer necessary
• The Startup class would be removed and its contents applied as applicable to the calls to WebApplicationBuilder in Program.cs
• Change to Blazor WebAssembly hosted templates tracked in Update blazorwasm-hosted templates to use minimal host #32471

[ghost]

Thanks for contacting us.

We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[Tratcher]

FYI @jmprieur @jennyf19

[jmprieur]

@DamianEdwards : are there examples of the new projects (or already converted templates?)?
cc: @Tratcher @jennyf19

[Tratcher]

@jmprieur see https://github.com/dotnet/aspnetcore/blob/b9efadc59ddbf6743775244622fb95301dd1846c/src/ProjectTemplates/Web.ProjectTemplates/content/EmptyWeb-CSharp/Program.cs

[jmprieur]

Thanks @Tratcher. I didn't even know that this could build.
Where would you do the services.AddAuthentication() ? and the app.UseAuthentication() ?

[Tratcher]

Services are on builder.Services, app.UseAuthentication() goes between the exception handlers and the routes.

We'll update the StarterWeb templates and then you can copy or iterate on those as needed.

[DamianEdwards]

@jmprieur you can see these changes WIP in #34016

[jmprieur]

@DamianEdwards : so you've done the work?
Should we then just update the templates to use the latest version of MIcrosoft.Identity.Web and its latest features?
cc: @jennyf19

[DamianEdwards]

@jmprieur sorry didn't realize the arrangement here that you typically update the parts of the files relevant to org auth. Would be great if you could update the templates to use latest version of Microsoft.Identity.Web and its latest features once my PR is in.

[jmprieur]

@DamianEdwards, there isn't really an arrangement.
but yes, I'll do that. Please tell me when it is

To test the updated templates, I installed VS2022 and .NET 6. Will that be enough? or should I install internal bits for the runtime and SDK? (and in that case where to get them from)?

[DamianEdwards]

It depends on how soon you want to test them. If you want to do it as soon as they're committed to the aspnetcore repo you'll need to set things up locally for development in the repo itself. Or you can wait until the changes flow to the SDK installer and then you can simply install a CI build from dotnet/installer

[DamianEdwards]

Fixed in #7699bab0fc5b1451272c7873af45990932d3d148