All 15 Background Tasks & Hosted Services questions
More in Background Tasks & Hosted Services
How should exceptions be handled inside a BackgroundService's work loop to prevent one failure from silently stopping all future processing? How do you implement a periodic scheduled task using PeriodicTimer instead of Task.Delay, and what problem does it solve? How do multiple independently-registered BackgroundServices coexist within the same application, and does registration order matter? What is the difference between IHostedService and the BackgroundService convenience base class? How would you configure a BackgroundService to fail fast and crash the host if a critical startup dependency (like a message broker) is unreachable? How does graceful shutdown work for a BackgroundService, and how should ExecuteAsync respect the CancellationToken? How would you implement a producer-consumer background processing pipeline using System.Threading.Channels alongside a BackgroundService? How would you implement a cron-like scheduled background job (e.g., 'run daily at 2 AM') without a third-party scheduling library? How do background services interact with health checks to signal their operational status to an orchestrator like Kubernetes? How would you implement retry logic with exponential backoff for a background service that calls a potentially-flaky external API?
Advertisement
ASP.NET Core › Background Tasks & Hosted Services

How does IHostApplicationLifetime let a BackgroundService react to application startup and shutdown events?

Intermediate

Answer

IHostApplicationLifetime exposes ApplicationStarted, ApplicationStopping, and ApplicationStopped CancellationTokens/events you can register callbacks against, letting a service run logic precisely when the application has fully started (useful for deferring work until all other services are ready) or precisely when shutdown begins (for final cleanup logic distinct from the service's own StopAsync).
public class MyService(IHostApplicationLifetime lifetime) : BackgroundService {
    protected override Task ExecuteAsync(CancellationToken stoppingToken) {
        lifetime.ApplicationStarted.Register(() => _logger.LogInformation("App fully started"));
        lifetime.ApplicationStopping.Register(() => _logger.LogInformation("App stopping..."));
        return Task.CompletedTask;
    }
}
Real-world example A service registration hook waits for ApplicationStarted before announcing itself to a service discovery system, ensuring it only advertises availability once the entire application (including all other hosted services) has successfully completed startup.

Common follow-ups: How does ApplicationStopping differ from the CancellationToken passed to ExecuteAsync?;What happens if a callback registered on ApplicationStopping throws an exception?

Hosting Models: Kestrel IIS & Reverse Proxies;Health Checks
All 15 Background Tasks & Hosted Services questions