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? 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? 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

What is the difference between Host.CreateApplicationBuilder and the older Host.CreateDefaultBuilder?

Intermediate

Answer

Host.CreateApplicationBuilder (introduced in .NET 7) is the modern, minimal-hosting-model-aligned builder returning a HostApplicationBuilder with more direct, immediate access to Services, Configuration, and Logging properties for a more streamlined top-level-statements-friendly syntax. Host.CreateDefaultBuilder (the older pattern, still supported) uses the more verbose builder-pattern-with-callbacks style (ConfigureServices, ConfigureAppConfiguration lambdas) common in .NET Core 2.x-6.x style Program.cs/Startup.cs files.
// Modern (.NET 7+)
var builder = Host.CreateApplicationBuilder(args);
builder.Services.AddHostedService<Worker>();
var host = builder.Build();

// Older style, still supported
var host = Host.CreateDefaultBuilder(args)
    .ConfigureServices((context, services) => {
        services.AddHostedService<Worker>();
    })
    .Build();
Real-world example A team modernizing an older Worker Service project migrates from the callback-heavy CreateDefaultBuilder pattern to CreateApplicationBuilder, reducing boilerplate and aligning with the same minimal hosting style used in their newer ASP.NET Core projects.

Common follow-ups: Are there any capabilities CreateDefaultBuilder has that CreateApplicationBuilder lacks?;How does this migration affect existing ConfigureServices callback code?

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