HangFire.Core
Metadata
Authors | Sergey Odinokov |
---|---|
Copyrights | Copyright © 2013-2015 Sergey Odinokov |
Description | Core components for Hangfire (background job system for ASP.NET applications). |
Owners | odinserj |
RequireLicenseAcceptance | False |
Dependencies | Owin:1.0|Newtonsoft.Json:5.0.0 |
Title | Hangfire Core Components |
PackageSize | 1007278 |
PackageHashAlgorithm | SHA512 |
PackageHash | lcQLsOmTiNzrH/MPBBaH078/GBZ4l6e/JUiQWIdyIxZlwzBw2Nf3NxMEiAZkCPIYFhkl1/7bxFoZe8oY93rnhw== |
DownloadCount | 000000 |
CreatedDate | 2015-10-01T14:30:48 |
ProjectUrl | http://hangfire.io/ |
LicenseUrl | https://raw.github.com/HangfireIO/Hangfire/master/LICENSE.md |
Summary | Background job processing for ASP.NET applications |
Tags | Hangfire OWIN Long-Running Background Fire-And-Forget Delayed Recurring Tasks Jobs Scheduler Threading Queues |
ReleaseNotes | http://hangfire.io/blog/ 1.5.0 * Added – `IBackgroundProcess` interface that allows to implement custom background processes. * Added – `BackgroundProcessingServer` class for creating a server instance with completely custom background processes. * Added – Support for running multiple `BackgroundJobServer` instances in the same AppDomain without explicit server names. * Added – `JobActivatorScope` class to support custom IoC scopes/lifetimes. * Added – Allow to specify a custom queue for recurring jobs (by @maleet). * Added – Allow to use CancellationToken type as a job method parameter. * Added – It is now possible to query the storage in state applying filters. * Added – Allow to pass custom filters to `BackgroundJobServer` via options. * Added – Option to hide the "Back to site" link (by @dradovic). * Changed – Server components and background processes now use `Task` with `TaskCreationOptions.LongRunning`. * Changed – ServerIds are now generated without ServerName, server names are deprecated. * Changed – Arguments Renderer now supports TimeSpan and DateTime (by @yngndrw). * Changed – Minor improvements for Dashboard navigation (by @pwelter34). * Changed – Worker does not process a job when a transition to the Processing state failed (by @yngndrw). * Changed – `BackgroundJobClientException` is thrown instead of `CreateJobFailedException`. * Changed – WorkerId is now auto-generated and based on a GUID. * Changed – Use StackTraceFormatter package for marking-up stack traces (by @atifaziz). * Changed – Updated Dashboard CSS to Twitter Bootstrap 3.3.5. * Fixed – Prevent worker from fetching and processing a job on shutdown. * Fixed – `TaskCanceledException` thrown from a job method leads to failed job as expected. * Fixed – Make `DelayedJobScheduler` resilient to empty background job ids. * Fixed – Logical error in SqlServerDistributedLockTimeout value check (by @Tom-Kelly). * Fixed – `OverflowException` in Dashboard when job duration exceeds int.MaxValue (by @mavenius). * Fixed – "More details" button in Dashboard changes to "Less details" when collapsed (by @pascalberger). |
Access
You can access data for this project using the tools and addresses described below.
NuGet (nuget.exe)
- Installing the package (HTTP Basic authentication):
-
nuget install HangFire.Core -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
nuget install HangFire.Core -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
NuGet (Package Manager Console)
- Installing the package (search all configured feeds):
-
Install-Package HangFire.Core
- Installing the package (HTTP Basic authentication):
-
Install-Package HangFire.Core -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
Install-Package HangFire.Core -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
- Uinstalling the package:
-
Uninstall-Package HangFire.Core
OpenWrap
- Installing the package:
-
o add-wrap HangFire.Core
- Uninstalling the package:
-
o remove-wrap HangFire.Core
Versions
A version is snapshot of a project's source code. It does not need to follow the Major.Minor.Revision.Build numbering pattern. It can be an arbitrary string of text that identifies a release or a build, in particular including meaningful words like beta, RC or RTM.