.NET Core support for Hangfire

[odinserj]

.NET Core support for Hangfire is here. The following projects that target .NET Standard 1.3 were added to the solution. I've tried xproj-based approach, but it is still weird and requires to change every aspect of a building pipeline. So I decided to end up with the portable projects.

.NET Core support is currently experimental, since there no unit tests that cover the .NET Standard target – not all the required dependencies are ported to .NET Core, including Moq (that requires Castle.Core, which NuGet package for .NET Core is broken currently). However, looks like it's working, at least on Windows.

A lot of dependencies are still in alpha or beta versions, so the final release will be available only when they are ready:

• NCrontab – not started
• CronExpressionDescriptor – not started
• Dapper – rc available
• Moq – alpha available
• Moq.Sequences – not started
• StackExchange.Redis – alpha available

Changes

There are no breaking changes for Hangfire on .NET 4.5. Consider .NET Core support as an add-on. However, some members became obsolete, but they will be removed only in 2.0.0, so you can use them for a while.

• Dashboard was abstracted from both OWIN and ASP.NET Core HTTP Abstractions.
• All methods that explicitly or implicitly require OWIN, such as IRequestDispatcher and RequestDispatcherContext types, became obsolete.
• DashboardOptions.AuthorizationFilters as well as IAuthorizationFilter interface are obsolete. Use IDashboardAuthorizationFilter interface and DashboardOptions.Authorization property instead.

Hangfire.Core.NetStandard

• CronExpressionDescriptor support was dropped, as no ILMerge available yet.
• DisplayNameAttribute support is not available yet.
• EntLibLogProvider, LoupeLogProvider and ElmahLogProvider were not ported (yet).

Hangfire.SqlServer.NetStandard

• TransactionScope-based transactions were replaced with DbTransaction (IPersistentJobQueue was changed to support this).
• Hangfire.SqlServer.MSMQ is not available on .NET Core.

Hangfire.AspNetCore

• IApplicationBuilder and IServiceCollection extension methods that allow to configure Hangfire with ease.
• AspNetCoreJobActivator that integrates with ASP.NET Core dependency injection system and knows what to do with scopes.
• AspNetCoreLogProvider that integrate Hangfire with ASP.NET Core logging subsystem.
• And of course, Dashboard UI is fully working.

How to use

Hangfire, Hangfire.Core, Hangfire.SqlServer and Hangfire.AspNetCore packages are already available on NuGet. They contain assemblies for both full .NET and .NET Core environments. So you can install them and play with Hangfire on .NET Core.

Installation is simple, as always. All you need is only to reference the special version 1.6.0-build-02111 in your project.json file:

"dependencies": {
    "Hangfire.Core": "1.6.0-build-02111",
    "Hangfire.SqlServer": "1.6.0-build-02111",
    "Hangfire.AspNetCore": "1.6.0-build-02111"
},

And configure your Startup class a bit:

using Microsoft.AspNetCore.Builder;
using Microsoft.Extensions.DependencyInjection;
using Hangfire;

namespace ConsoleApplication
{
    public class Startup
    {
        public void ConfigureServices(IServiceCollection services)
        {
            services.AddHangfire(configuration => configuration
                .UseSqlServerStorage(@"server=.\sqlexpress;database=Hangfire.Test4;integrated security=sspi;"));
        }

        public void Configure(IApplicationBuilder app)
        {
            app.UseHangfireDashboard(); // Will be available under http://localhost:5000/hangfire
            app.UseHangfireServer();

            BackgroundJob.Enqueue(() => Console.WriteLine("Hello, .NET Core!"));
        }
    }
}

Closes #591, #476, #365 and #267.