HangfireIO / HangfireIO/Hangfire

Hangfire cannot be used in the 'ASP.NET Core Web Application(.NET Framework)' template of Visual Studio 2015 with update3

Open
#781 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
10.1k
Forks
1.8k
Avg merge
1h 19m
Merged PRs (30d)
1

Description

as the problem shows, hangfire cannot be used in the 'ASP.NET Core Web Application(.NET Framework)' template of Visual Studio 2015 with update3. There is no proper extension methods for `IServiceCollection` to use Hangfire, neither 'services.AddHangfire(x => x.UseSqlServerStorage(""));' nor 'GlobalConfiguration.Configuration.UseSqlServerStorage("");'

So, did I do something wrong, or I just misunderstood something what I have learned from your docment. I just say, after all, hangfire has supported the asp.net core, there is no reason I can't use it in the ASP.NET Core Web Application(.NET Framework)

Please give me some help, Thank you very much (some Chinese have tried their best even just wrote those simple English words like me, huh :) )

updated in 2017.1.3 14:45:54
Few minutes passed, I decided to change the 'frameworks' node from 'net452' to 'netstandard1.3' in the project.json, it finally worked. But if someone could explain the reason for me, I will appreciate it, huhah~

updated in 2017-1-3 14:56:03
Yeah, me again. Ten minutes passed, I refferenced the 'Hangfire.AspNetCore' package in the project, and the 'frameworks' node still remained 'net452', it also worked.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the ASP.NET Core Web Application (.NET Framework) template in Visual Studio 2015 Update 3 and inspect its project.json frameworks node and Hangfire package references. Compare the net452 and netstandard1.3 cases described here; done means determining whether the template is supported and documenting the required framework and Hangfire.AspNetCore reference.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.