NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet · #2596 most downloaded on NuGet
Autofac IoC Container integration support for Hangfire (background job framework for .NET applications).
Last release 2 years ago
no release in 18 months
Ships unpredictably
gaps range from 2 weeks to 6.0 years
Most releases are documented
notes for 10 of 16 stable releases
2 versions withdrawn
withdrawn after publishing
127 years old
21 releases · first in 1900
https://github.com/HangfireIO/Hangfire.Autofac/releases 2.7.0
https://github.com/HangfireIO/Hangfire.Autofac/releases 2.7.0
2.6.0
HangfireIO as a NuGet package owner.2.5.0
Microsoft.CodeAnalysis.NetAnalyzers package.2.4.1
netstandard2.0 target to the NuGet package.2.4.0
netstandard2.0 target support for the package.2.3.1
2.3.0
2.2.0
2.1.0
2.0.1
AutofacJobActivator.LifetimeScopeTag field is now public.One column per quarter.
https://github.com/HangfireIO/Hangfire.Autofac/releases 2.6.0
https://github.com/HangfireIO/Hangfire.Autofac/releases 2.6.0
HangfireIO as a NuGet package owner.2.5.0
Microsoft.CodeAnalysis.NetAnalyzers package.2.4.1
netstandard2.0 target to the NuGet package.2.4.0
netstandard2.0 target support for the package.2.3.1
2.3.0
2.2.0
2.1.0
2.0.1
AutofacJobActivator.LifetimeScopeTag field is now public.https://github.com/HangfireIO/Hangfire.Autofac/releases 2.5.0
https://github.com/HangfireIO/Hangfire.Autofac/releases 2.5.0
Microsoft.CodeAnalysis.NetAnalyzers package.2.4.1
netstandard2.0 target to the NuGet package.2.4.0
netstandard2.0 target support for the package.2.3.1
2.3.0
2.2.0
2.1.0
2.0.1
AutofacJobActivator.LifetimeScopeTag field is now public.https://github.com/HangfireIO/Hangfire.Autofac/releases 2.4.1
https://github.com/HangfireIO/Hangfire.Autofac/releases 2.4.1
netstandard2.0 target to the NuGet package.2.4.0
netstandard2.0 target support for the package.2.3.1
2.3.0
2.2.0
2.1.0
2.0.1
AutofacJobActivator.LifetimeScopeTag field is now public.netstandard2.0 target to the NuGet package.https://github.com/HangfireIO/Hangfire.Autofac/releases 2.4.0
https://github.com/HangfireIO/Hangfire.Autofac/releases 2.4.0
netstandard2.0 target support for the package.2.3.1
2.3.0
2.2.0
2.1.0
2.0.1
AutofacJobActivator.LifetimeScopeTag field is now public.netstandard2.0 target support for the package based on Autofac 5.0.Changed – NuGet package title and a link to the project site were added.
2.3.1
2.3.0
2.2.0
2.1.0
2.0.1
AutofacJobActivator.LifetimeScopeTag field is now public.Added – Support for .NET Core with .NET Standard 1.3.
2.3.0
2.2.0
2.1.0
2.0.1
AutofacJobActivator.LifetimeScopeTag field is now public.Added – Allow combining lifetime scope tags (by @chaoaretasty).
2.2.0
2.1.0
2.0.1
AutofacJobActivator.LifetimeScopeTag field is now public.Added – Ability to use non-tagged nested lifetime scopes.
2.1.0
2.0.1
AutofacJobActivator.LifetimeScopeTag field is now public.Changed – AutofacJobActivator.LifetimeScopeTag field is now public.
2.0.1
AutofacJobActivator.LifetimeScopeTag field is now public.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Hangfire.Autofac now resolves service instances using a child, tagged lifetime scope. Added shared instance and deterministic disposal features suppor
Hangfire.Autofac now resolves service instances using a child, tagged lifetime scope. Added shared instance and deterministic disposal features support allowed by the new JobActivatorScope abstraction introduced in Hangfire 1.5.0-beta1.
Please see the updated README.md file for the details.
Ownership of all the resolved components moved to Autofac, ownership in this case means the party which is responsible to call the Dispose method on IDisposable instances. Now Autofac itself is responsible for disposing the resolved components.
Previously job type instances (i.e. an instance of a type parameter passed to Enqueue, Schedule, etc. methods) were owned by Hangfire itself and thus the Dispose method was called by Hangfire. It was also beleived that your job type is responsible for disposing all the passed dependencies (through the constructor or properties).
Now, as the ownership moved, it is not necessary to call the Dispose method on the dependencies – it will be called automatically by Autofac (if appropriate). So your Dispose methods may be called multiple times, but generally this is not a problem.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →