All 15 Generic Host questions
More in Generic Host
What does calling host.Run() versus host.RunAsync() do, and when would you use each? What is the difference between Host.CreateApplicationBuilder and the older Host.CreateDefaultBuilder? How does the Generic Host integrate configuration, logging, and dependency injection into a single unified builder? What is IHostEnvironment, and how do you use it to conditionally configure services based on the current environment? What is the role of IHostLifetime, and how does it differ across console applications, Windows Services, and containers? How do you access the built IHost's service provider after Build() to resolve services outside the normal request/injection flow, such as in Program.cs itself? How do you configure the Generic Host to read configuration from a custom file format or remote source before the rest of the application starts? How does the Generic Host manage the application's startup and shutdown lifecycle, including handling OS signals like SIGTERM? How would you build a console application that supports both interactive command execution and long-running hosted service behavior using the Generic Host? How does the Generic Host's dependency validation (ValidateOnBuild and ValidateScopes) help catch DI configuration errors early?
Advertisement
.NET › Generic Host

How do you register configuration and services differently for a Worker Service running as a Windows Service or systemd daemon?

Intermediate

Answer

The Microsoft.Extensions.Hosting.WindowsServices and Microsoft.Extensions.Hosting.Systemd packages provide UseWindowsService() and UseSystemd() extension methods that configure the host to properly integrate with the respective OS service manager -- handling service-specific lifecycle events, logging redirection (to the Windows Event Log or systemd journal), and correct working directory resolution, which differ from running as a plain console application interactively.
var builder = Host.CreateApplicationBuilder(args);
builder.Services.AddWindowsService(options => options.ServiceName = "MyWorkerService");
builder.Services.AddSystemd();
builder.Services.AddHostedService<Worker>();

var host = builder.Build();
host.Run();  // automatically detects and adapts to the actual hosting context
Real-world example A Worker Service deployed as a Windows Service in one environment and as a systemd daemon on Linux in another uses both AddWindowsService and AddSystemd registrations simultaneously, with the host automatically detecting and adapting to whichever context it's actually running under.

Common follow-ups: What logging differences occur when running under systemd versus interactively?;How do you install and manage a .NET Worker Service as an actual Windows Service?

Docker & Containerization;Logging
All 15 Generic Host questions