All 15 Generic Host questions
More in Generic Host
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? How do you register configuration and services differently for a Worker Service running as a Windows Service or systemd daemon? 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? How would you implement a startup task that must complete successfully before the Generic Host considers the application ready to serve traffic or process work?
Advertisement
.NET › Generic Host

What is the role of IHostLifetime, and how does it differ across console applications, Windows Services, and containers?

Intermediate

Answer

IHostLifetime is the abstraction responsible for actually starting and stopping the host in a way appropriate to its hosting environment -- ConsoleLifetime (default) listens for Ctrl+C/SIGTERM signals directly, WindowsServiceLifetime integrates with the Windows Service Control Manager's start/stop commands, and SystemdLifetime integrates with systemd's service notification protocol -- letting the same application code run correctly whether launched interactively, as an installed OS service, or inside a container, with the host automatically selecting the appropriate implementation via UseWindowsService()/UseSystemd() or defaulting to ConsoleLifetime.
// Default: ConsoleLifetime, handles Ctrl+C and SIGTERM directly
var host = Host.CreateApplicationBuilder(args).Build();

// Explicit: WindowsServiceLifetime, integrates with Windows SCM
builder.Services.AddWindowsService();  // swaps in WindowsServiceLifetime when actually running as a service
Real-world example A single Worker Service codebase runs identically in a developer's console during debugging (ConsoleLifetime) and as a production Windows Service (WindowsServiceLifetime), with the host automatically selecting the correct lifetime implementation for each context.

Common follow-ups: How would you write a custom IHostLifetime for an unsupported hosting scenario?;What happens if UseWindowsService() is called but the app isn't actually running as a Windows Service?

Background Services;.NET CLI SDK & Project Structure (csproj)
All 15 Generic Host questions