If you need your WebJob to run a task and exit, or if you need to conditionally exit it under certain scenarios, and you thought it’s just a matter of exiting the worker service’s
ExecuteAsync method, you’d be wrong. Even after your worker code has stopped running, the parent host stays alive. The right way to exit your WebJob is to inject
IHostApplicationLifetime into your worker, and then the last line of code in your
ExecuteAsync would be a call to its
public Worker(ILogger<Worker> logger, IHostApplicationLifetime appLifeTime)
_logger = logger;
_appLifetime = appLifeTime;
protected override async Task ExecuteAsync(CancellationToken stoppingToken)
int runs = 0;
while (!stoppingToken.IsCancellationRequested && runs++ < 3)
await Task.Delay(2000, stoppingToken);
Nish Nishant is a technology enthusiast from Columbus, Ohio. He has over 20 years of software industry experience in various roles including Chief Technology Officer, Senior Solution Architect, Lead Software Architect, Principal Software Engineer, and Engineering/Architecture Team Leader. Nish is a 14-time recipient of the Microsoft Visual C++ MVP Award.
Nish authored C++/CLI in Action for Manning Publications in 2005, and co-authored Extending MFC Applications with the .NET Framework for Addison Wesley in 2003. In addition, he has over 140 published technology articles on CodeProject.com and another 250+ blog articles on his WordPress blog. Nish is experienced in technology leadership, solution architecture, software architecture, cloud development (AWS and Azure), REST services, software engineering best practices, CI/CD, mentoring, and directing all stages of software development.
Nish's Technology Blog