Hangfire 1.7.0 is finally released with the whole bunch of new features and improvements for background processing, background and recurring jobs, SQL Server storage, .NET Core integration and interoperability between .NET platforms to provide a strong foundation for future features and extensions.
Continue Reading →rss feed Blog
Hangfire 1.7.0
-
by
@odinserj
- release, hangfire-core
- 0 Comments
- Edit on GitHub
Hangfire 1.7.0 RC
-
by
@odinserj
- release, hangfire-core
- 0 Comments
- Edit on GitHub
This is a release candidate for the upcoming version 1.7.0 with a lot of new features and improvements for almost all the aspects of background job processing. Below you’ll find a short list of them as well as upgrade details, and more information will be published later. Please note this is a pre-release, and it’s not suitable for critical environments.
Continue Reading →Hangfire 1.6.23
-
by
@odinserj
- release, hangfire-core
- 0 Comments
- Edit on GitHub
This version fixes some issues and acts as an optional trampoline to the upcoming 1.7.0 release to simplify the rolling upgrades. So your current servers will work side-by-side with the newer ones even if you are using SQL Server as a job storage and applied the new migration. There will be more information on upgrading, but this version is nice-to-have (but not required) anyway.
Continue Reading →Hangfire.Pro.Redis 2.4.0
-
by
@odinserj
- release, hangfire-pro
- 0 Comments
- Edit on GitHub
This is an important release that makes timeout detection much more robust. First of all, Redis server itself now acts as a single time authority for performing timeout checks for both jobs and servers rather than UTC time of a current Hangfire Server. So you don’t need to use synchronized clocks to prevent false positives for timeout checks.
Continue Reading →Hangfire 1.6.22
-
by
@odinserj
- release, hangfire-core
- 0 Comments
- Edit on GitHub
This version finally fixes interoperability issues that arise, because primitive built-in types like String reside in assemblies with different name in .NET Core (System.Private.CoreLib.dll) and .NET Framework (mscorlib.dll). This led to JobLoadException in .NET Framework-based applications, when they tried to perform background jobs created by a .NET Core-based one. The new version solves this problem by re-writing assembly name when resolving a type for a job and its parameters.