Background Tasks Without a Separate Service: Hangfire for ASP.NET 

Thank you so much for joining, asking questions, and checking out this video here on youtube :)

Thank you for posting this video! Starting to work with Hangfire for my job and this was a great introduction to how it works!

Just starting to learn Hangfire. Nice explanation.

Thanks for info. Can you explain what happens to your hangfire jobs, if the IIS machine that is hosting the website, crashes, gets restarted for any reason? And what if the IIS machine is running fine, but the MSSQL server goes down without warning? Do you have recommendations on how to recover from those situations? It seems to me, that hangfire is 100% counting on the Application pool that is hosting the web site (that has hangfire enabled in it) to be up and running 100% of the time. And if not, then hangfire cannot process the jobs....is that correct? So, basically if IIS is down, so is hangfire.

Should I get the source code link? I want to check for reference.

There is a NuGet package that allows you to use in memory as the job store instead of a persistent solution like sql server

Thanks !

Good Explanation.

Code link is missing. Can you please add that?

One other question, so is hangfire running in a non UI thread (background thread) in the asp.net web application? I believe that is what is going on with it. So therefore it doesnt ever block the UI.

Does hangfire support kerberos authentication?

Hi Matthew, Can you pls tell if i want to return other class properties how it can be returned through BackgroundJob.Enqueue(). Or it just only returns the job id ? Can we use any other method of hangfire which can return all class properties of method which we are calling ?

Link to the code please.

Good explanation. It will be better sharing the source code with us. Could you please share the source code?

Quartz.net is just as easy to use as Hangfire, if not easier.