Missing code for .NET 6.0

[JoshClose]

.NET 6.0 uses WebApplicationBuilder. For this to work, some modifications need to be made. I was not able to get this to run without these.

https://stackoverflow.com/questions/70571849/host-asp-net-6-in-a-windows-service

var webApplicationOptions = new WebApplicationOptions
{ 
    ContentRootPath = AppContext.BaseDirectory, 
    Args = args, 
    ApplicationName = System.Diagnostics.Process.GetCurrentProcess().ProcessName 
};
var builder = WebApplication.CreateBuilder(webApplicationOptions);

builder.Host.UseWindowsService();

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: b0bd8cb8-7e28-8c4d-a550-3aea8f3ab4dd
• Version Independent ID: 4b60d24e-ef05-15e5-10b4-483094081bf3
• Content: Host ASP.NET Core in a Windows Service
• Content Source: aspnetcore/host-and-deploy/windows-service.md
• Product: aspnet-core
• Technology: aspnetcore-hostdeploy
• GitHub Login: @Rick-Anderson
• Microsoft Alias: riande

[Rick-Anderson]

Thanks for reporting.
Any chance you could PR this? At the top right of the article, select the Edit pen icon:

Select the pen icon again. Save.

[JoshClose]

I'll give it a shot.

[JoshClose]

Looks like there are some unresolved issues for this. You are in on the conversation on the docs one. Seems like the solution that @davidfowl suggests is setting the --contentRoot instead of changing the WebApplicationOptions.

dotnet/runtime#69212
dotnet/aspnetcore#37464
#23387

I tried this and it works fine that way.

I updated the doc to change the PowerShell New-Service command to use --contentRoot instead of the other code.

#25882

[Rick-Anderson]

Nice work!