2.6.0

Release Notes

• Project – Sign NuGet package and .NET assemblies on build.
• Project – Enable NuGet package signature validation on restore.
• Project – Use deterministic and locked package restore for all projects.
• Project – Add more metadata for assemblies and NuGet package.
• Project – Fix GitHub repository URL in the nuspec file.
• Project – Add HangfireIO as a NuGet package owner.

2.5.0

Release Notes

• Project – Full source link support with embedded symbols and repository-based sources.
• Project – Enable static analysis via the Microsoft.CodeAnalysis.NetAnalyzers package.
• Project – Restore packages in locked mode for all the projects.
• Project – Switch from MSTest to Xunit for simplicity across other projects.

2.4.1

Release Notes

• Fixed – Add missing files for the netstandard2.0 target to the NuGet package.

2.4.0

Release Notes

• Added – netstandard2.0 target support for the package based on Autofac 5.0.

2.3.1

Release Notes

• Changed – NuGet package title and a link to the project site were added.

2.3.0

Release Notes

• Added – Support for .NET Core with .NET Standard 1.3.
• Added – Support for SourceLink 2.0. If "Enable source link support flag is set" in Visual Studio it's possible to debug Hangfire.Autofac using its downloaded sources.
• Changed – Removed references to Newtonsoft.Json and Owin packages.
• Changed – Renamed HangFire.Autofac to Hangfire.Autofac.

2.2.0

Release Notes

• Added – Allow combining lifetime scope tags (by @chaoaretasty).

1.2.0-beta1

Release Notes

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.

Updating

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.

0.1

Initial version of HangFire.Autofac