hangfire

I got a SaaS project that needs the use Hangfire. We already implemented the requirements to identify a tenant. Architecture Persistence Layer Each tenant has it's own database .NET Core We already have a service TenantCurrentService which returns the ID of the tenant, from a list of source [hostname, query string, etc] We already have a DbContextFactory for Entity Framework which return a DB context with the correct connection string for the client We are currently using ASP.NET Core DI (willing to change if that helps) Hangfire Using single storage (eg: Postgresql), no matter the tenant

I'm rewriting this entire question because I realize the cause, but still need a solution: I have a recurring job in Hangfire that runs every minute and check the database, possibly updates some stuff, then exits. I inject my dbcontext into the class containing the job method. I register this dbcontext to get injected using the following builder.RegisterType<ApplicationDbContext>().As<ApplicationDbContext>().InstancePerLifetimeScope(); However, it seems that Hangfire does not create a seperate lifetime scope every time the job runs, because the constructor only gets called once, although the

I am having following application : 1) Mvc app : Hangfire client from where i will just enqueue jobs and host dashboard.This app will contains reference of my class library. 2) Console App : Hangfire server will live in this console application. 3) Class library : Shared library between hangfire server(Console app) and hangfire client(asp.net mvc) where my long running code will reside.Hangfire server will execute code of this library. I am having structure like below in Class library following strategy design pattern. Code taken from following : Reference: Interfaces: public interface

In my web application (ASP.NET Core), I want to run a job in the background that is listening to a remote server, calculating some results and pushing it to the client on Pusher (a websocket). I'm not sure where I'm supposed to start this task. Currently I start it at the end of public void Configure(IApplicationBuilder app, IHostingEnvironment env) in Startup.cs but I think there is something wrong about that, it doesn't make sense to start background jobs in a method called "Configure". I was expecting to find a Start method somewhere Also, when I try to use EF Core to generate initial

I am using Hangfire and like the software very much! But one thing I am missing is how to add a recurring job that executes every few minutes (e.g. every 15 minutes). Is there a way to achieve this? Currently I am using this approach: RecurringJob.AddOrUpdate(() => Console.Write("Recurring"), "*/15 * * * *"); And is working like a charm. Reference to my question in Hangfire forums: http://discuss.hangfire.io/t/how-to-create-cron-job-that-is-executing-every-15-minutes/533 Looking at Hangfire.Cron class I don't know if it's possible. A workaround would be to create four different schedules i.e:

How can I use .net core's default dependency injection in Hangfire ? I am new to Hangfire and searching for an example which works with asp.net core. See full example on GitHub https://github.com/gonzigonz/HangfireCore-Example . Live site at http://hangfirecore.azurewebsites.net/ Make sure you have the Core version of Hangfire: dotnet add package Hangfire.AspNetCore Configure your IoC by defining a JobActivator . Below is the config for use with the default asp.net core container service: public class HangfireActivator : Hangfire.JobActivator { private readonly IServiceProvider

I am running HangFire within my MVC web app but whenever I try to navigate to http://MyApp/hangfire , it redirects me to my app's login page as though I am not logged in. I have not explicitly configured any requirements for authorization...e.g. I had the below in the web.config, but then took it out in attempts to get this to work. <location path="hangfire"> <system.web> <authorization> <allow roles="Administrator" /> <deny users="*" /> </authorization> </system.web> In theory, this is what I'd want, and when I log into my main web application, I will be logged in with an Administrator role