All 15 Generic Host questions
More in Generic Host
What is the Generic Host in .NET, and what problem does it standardize across different application types? 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? 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? 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?
Advertisement
Back to results for “Dependency Injection”
.NET › Generic Host

How does the Generic Host integrate configuration, logging, and dependency injection into a single unified builder?

Intermediate

Answer

HostApplicationBuilder (and its WebApplicationBuilder subclass) exposes .Configuration (an IConfigurationBuilder pre-populated with the standard providers), .Services (an IServiceCollection for DI registration), and .Logging (an ILoggingBuilder for configuring log providers) as properties on the same builder object -- letting you configure all three cross-cutting concerns in one linear, readable sequence before calling .Build() to produce the fully wired IHost, rather than juggling separate configuration objects or nested callback lambdas.
var builder = Host.CreateApplicationBuilder(args);

// All three configured through the same builder instance
builder.Configuration.AddJsonFile("custom-settings.json");
builder.Services.AddHostedService<Worker>();
builder.Logging.AddConsole().SetMinimumLevel(LogLevel.Debug);

var host = builder.Build();
host.Run();
Real-world example A Worker Service's Program.cs reads clearly top-to-bottom -- configuration sources, then service registrations, then logging setup -- all through the same builder variable, making the entire application's cross-cutting setup visible in one place rather than scattered across multiple configuration methods.

Common follow-ups: How does this unified builder pattern compare to the older Startup.cs ConfigureServices/Configure split?;What happens if you try to modify builder.Services after calling Build()?

Configuration & Options;Logging
All 15 Generic Host questions