Hangfire.AspNetCore 1.8.24

ASP.NET Core support for Hangfire, a background job framework for .NET applications.

Showing the top 20 packages that depend on Hangfire.AspNetCore.

Packages Downloads
Hangfire
An easy and reliable way to perform fire-and-forget, delayed and recurring, long-running, short-running, CPU or I/O intensive tasks inside ASP.NET applications. No Windows Service / Task Scheduler required. Even ASP.NET is not required. Backed by Redis, SQL Server, SQL Azure or MSMQ. This is a .NET alternative to Sidekiq, Resque and Celery. https://www.hangfire.io/
67
Hangfire
An easy and reliable way to perform fire-and-forget, delayed and recurring, long-running, short-running, CPU or I/O intensive tasks inside ASP.NET applications. No Windows Service / Task Scheduler required. Even ASP.NET is not required. Backed by Redis, SQL Server, SQL Azure or MSMQ. This is a .NET alternative to Sidekiq, Resque and Celery. https://www.hangfire.io/
6
Hangfire
An easy and reliable way to perform fire-and-forget, delayed and recurring, long-running, short-running, CPU or I/O intensive tasks inside ASP.NET applications. No Windows Service / Task Scheduler required. Even ASP.NET is not required. Backed by Redis, SQL Server, SQL Azure or MSMQ. This is a .NET alternative to Sidekiq, Resque and Celery. https://www.hangfire.io/
4
Hangfire
An easy and reliable way to perform fire-and-forget, delayed and recurring, long-running, short-running, CPU or I/O intensive tasks inside ASP.NET applications. No Windows Service / Task Scheduler required. Even ASP.NET is not required. Backed by Redis, SQL Server, SQL Azure or MSMQ. This is a .NET alternative to Sidekiq, Resque and Celery. https://www.hangfire.io/
1
Hangfire
An easy and reliable way to perform fire-and-forget, delayed and recurring long-running, short-running, CPU or I/O intensive tasks inside ASP.NET application. No Windows Service / Task Scheduler required. Even ASP.NET is not required. Backed by Redis, SQL Server, SQL Azure or MSMQ. This is a .NET alternative to Sidekiq, Resque and Celery. http://hangfire.io/
1

Release notes are available in our blog https://www.hangfire.io/blog/ Please see https://docs.hangfire.io/en/latest/upgrade-guides/upgrading-to-hangfire-1.8.html to learn how to upgrade.

1.8.23 • Fixed – InvalidOperationException: The request reached the end of the pipeline without executing the endpoint.

1.8.22 • Added – MapHangfireDashboardWithNoAuthorizationFilters method, which does not include local-only filters. • Changed – Set 404 status code when MapHangfireDashboard is used and no dispatcher is found. • Fixed – InvalidOperationException upon receiving a request for 'hangfire/bootstrap.min.css.map'.

1.8.18 • Fixed – Swallow possible ObjectDisposedException in the StopAsync method. • Fixed – Avoid NullReferenceException when LocalIpAddress or RemoteIpAddress is null.

1.8.10 • Fixed – Don't check HasStarted in Response.WriteAsync to avoid breaking dispatchers. • Project – Enable NuGet package and DLL signing with a company certificate. • Project – Require NuGet package signature validation on restore for dependencies. • Project – Add HangfireIO as a package owner.

1.8.9 • Fixed – Don't attempt to write response headers when response has already started (by @maliming). • Project – Enable full source link support with embedded symbols and repository-based sources. • Project – Enable repeatable package restore using a lock file.

1.8.0 • Breaking – Make the package to be dependent on Hangfire.NetCore and use the same types. • Added – IApplicationBuilder.UseHangfireServer that accepts custom factory for IBackgroundProcessingServer.

Version Downloads Last updated
1.8.24 9 08/11/2026
1.8.23 90 05/20/2026
1.8.22 4 06/28/2026
1.8.21 14 05/26/2026
1.8.17 6 05/20/2026
1.8.12 1 06/09/2026
1.7.33 12 05/21/2026