Releases: HangfireIO/Hangfire.Ninject
Releases · HangfireIO/Hangfire.Ninject
2.0.0
Release Notes
- Breaking – Use the
NinjectJobActivatorScope.Current
scope instead of theJobActivatorScope.Current
for deterministic disposal. - Added – Add
netstandard2.0
andnet46
targets for newer applications. - Fixed – Correct deterministic disposal for async contexts in
net46
andnetstandard2.0
platforms. - Project – Add readme and icon for the NuGet package.
- Project – Sign NuGet and assembly artifacts during the build process with a company's own certificate.
- Project – Full source link support with embedded symbols and repository-based sources.
- Project – Require NuGet package signature validation on restore.
- Project – Use deterministic and locked package restore for dependencies.
- Project – Enable static analysis via the
Microsoft.CodeAnalysis.NetAnalyzers
package. - Project – Modernize the build system and project files to use newest features.
1.2.0-beta1
Hangfire.Ninject is updated to support the new JobActivatorScope
class introduced in Hangfire 1.5.0-beta1. It is much simpler now to use the Ninject IoC container with Hangfire now.
Release Notes
- Added
InBackgroundJobScope
andInRequestOrBackgroundJobScope
methods to re-use instances that are already created in current background job processing scope. - Ninject's Cache-and-collect lifecycle management is used to work with
IDisposable
instances.
Updating
Due to the implications of the cache-and-collect system (please see the link above), IDisposable
instances are disposed in a deterministic manner only when a binding reduced to a corresponding scope. Instances of dependencies that are not scoped will be disposed on next GC run (Ninject uses weak references). So please update all your bindings using the InBackgroundJobScope
or InRequestOrBackgroundJobScope
methods.