Running Background tasks using IHostedService and BackgroundService (In ASP.NET Core 3.1)

[@MineFreeman]

Great! Clearly talk about how the backgroundservice work with Controller, thx a lot~

[@DotNetCoreCentral]

@Mine Freeman, thanks for watching!

[@vineettomar4823]

Hi, I've a scenario. Suppose we have created one job that completes execution within 20 minutes and runs on a time interval of 10 minutes, but if job takes more time (10 minutes more) in execution, then time interval should adjust automatically. Ex - Suppose a job starts at 10:00AM and completes execution at 10:20AM. Again job will start @10:30AM with the interval of 10 minutes. If Job takes 10 more minutes in execution and completes execution @10:30AM, then again job should start @10:40AM rather than @10:30AM. Interval time should be increased according to time taken in execution (It should be changed dynamically.)

[@DeepWorksStudios]

Did you figured it out? If not i offer you my help :)

[@ManiasInc]

Excellent explanation man!! Thanks a lot!! 🎉🎉👏👏🚀

[@MihaiMoisei]

Thank you for the clear presentation.

[@DotNetCoreCentral]

Mihai Moisei thanks for watching!

[@shipravats536]

Amazing explanation and very help full video.

[@DotNetCoreCentral]

Glad it was helpful!

[@davidemmanuel3001]

Great video

[@microtech2448]

This background task is something which is running at regular interval but how can we schedule multiple jobs and pause/resume them if needed with their own independent frequency/interval and monitor them through a UI?

[@minchaudhary]

Thank you, you made me clear about background service

[@DotNetCoreCentral]

@Min Chaudhary, thanks for watching!

[@ost7487]

Straight to the point. Thanks.

[@DotNetCoreCentral]

@Saitama, thanks for watching!

[@rvrby2541]

Very useful, thank you very much!

[@DotNetCoreCentral]

RvR By thanks for watching!

[@saarcfashion1196]

It's better if you would have added the implementation of stopping the Background Service. By the way, good job.

[@JeffMTX]

When you have such a task running in the background, is there any straightforward way for it to communicate its status so that external processes (eg the one that spawned it) can access that status?

[@DotNetCoreCentral]

@J M, there are a couple of ways to achieve it. 1. is to create an in-memory queue and communicate through it. 2. is to create an event exchange and communicate through that. One thing to keep in mind is that, since they are in different threads, the code needs to be thread-safe.

[@noelbrantley3400]

i know it is kinda randomly asking but do anybody know a good place to watch new movies online ?

[@PrabinYovan]

Awesome video, thank you so much

[@DotNetCoreCentral]

Prabin Yovan thanks for watching!

[@StefanoLabate]

very useful, thank you!

[@DotNetCoreCentral]

Stefano Labate thanks for watching!

[@toetoeag]

Thank you. Good explanation.

[@DotNetCoreCentral]

@ToeToe Aung, thanks for watching!

[@shahjahan12003]

Thanks a lot. Very much helpful.

[@DotNetCoreCentral]

@Mohammad Shahjahan Mia, thanks for watching!

[@illuminaticat4861]

Important to note that adding the hosted service for method 1 does not work when adding it from startup configureServices, and requires to be added through program createHostBuilder.

[@DotNetCoreCentral]

@IlluminatiCat, I am not sure I understand, can you refer to the minute in the video where you see the issue is?

[@khertgeverola175]

Hi, great content. Is it possible to run BackgroundService on demand ? Lets say, every API call I want to trigger the backgroundservice.

[@ukaigwechidi6563]

@DotNet Core Central, please kindly leave a reply to this question above ... @Geverola, I would appreciate you sharing the answer to this if you have got one ...

[@schweppesmandarin8839]

Amazing tutorial!

[@DotNetCoreCentral]

@Schweppes Mandarin, thanks!

[@schweppesmandarin8839]

@@DotNetCoreCentral I sent you an email but I did not receive a response yet

[@ArkopalBhattacharya]

very well explained!

[@DotNetCoreCentral]

@Arkopal Bhattacharya, thanks for watching!

[@smrutiranipatro102]

How do we deploy this on IIS and test whether background service is running without failure?

[@merttatlsetsis3350]

Hi, did you find anything about hosting service to IIS

[@bilalelmursi4039]

thank you!

[@DotNetCoreCentral]

@Bilal Elmursi, thanks for watching!

[@mscotthowell1]

Great work.

[@DotNetCoreCentral]

@Scott Howell thanks!

[@codewithkashif]

Great content! So what is the difference between IhostedService vs BackgroundService approach Realtime example of When should use which one.

[@DotNetCoreCentral]

@Kashif Reza, if you need control over how to start and stop your service, you go with IHostedService, otherwise, BackgroundService will be the better approach. Having said that, I personally prefer IHostedService, just my personal preference.

[@nguyenvantrinh4924]

thank bro

[@DotNetCoreCentral]

Thanks for watching!

[@aymanmetwally5560]

Great

[@DotNetCoreCentral]

@ayman metwally thanks for watching!

[@aj.arunkumar]

is there a way to manually start background job from an Action method instead of at starttime ?

[@DotNetCoreCentral]

Not that I know of.

[@aargomemnon]

Thanks for this video. I learned a lot. Also is it possible to manually start and stop this service with UI?

[@DotNetCoreCentral]

@Gama Sharma, thanks for watching! Yes, you can do it, but you will need to expose this through an API.

[@microtech2448]

@@DotNetCoreCentral can you please give example of this? Also, can we create dashboard or persist ongoing tasks in database and process them and see their status updated over time just like in hangfire?

[@parko1965]

Good work, now I can write PHP task using Cron Tab in C#, how technology is moving.

[@DotNetCoreCentral]

@Davey Lad, thanks for watching!

[@rajkumar-oy3ni]

Thank you for the video, but here how do we return response to UI once completed

[@DotNetCoreCentral]

@raj kumar, if you want a response to a background job to be returned to the UI, there are multiple ways of doing it. SignalR is one of them.

[@musandlala7991]

Lovely work. I am wondering how safe would this be for running automated Entity Framework calls

[@DotNetCoreCentral]

@Kmn I, thanks for watching! With respect to running background jobs to access EF calls, I do not see any reason why it would be unsafe. Unless the query ran can cause potential deadlocks, in which case anyway the design has to be rethought. Let me know if it makes sense. Thanks

[@sornt]

thank you. What is the best option to select for you?

[@DotNetCoreCentral]

Sorn Toomgasorn thanks for watching! I prefer using first option of interface as interface always give you more flexibility.

[@sornt]

DotNet Core Central thank you for your reply.

[@DotNetCoreCentral]

Sorn Toomgasorn you are welcome!

[@ashutoshmishra2170]

Hi sir, I have a requirement like one process get executed on every 1st day of month . how to achieve this . please reply.

[@DotNetCoreCentral]

@Ashutosh Mishra , for that requirement, you should use Hangfire. I have a video here: kzbin.info/www/bejne/qYLcimOuq69nY9E

[@c-sharptricks9899]

but where is code to make it reapeat after specific intervals. i want it to be a scheduled job. task.delay is just to create a delay after performing dowork. but no code to make it scehduled job. please help

[@DotNetCoreCentral]

@C-Sharp Tricks , if you want scheduled jobs, the better option is to use Hangfire. I have a video here: kzbin.info/www/bejne/qYLcimOuq69nY9E

[@rajkumar-oy3ni]

is it like fire and forget and do we need to do pooling to find whether the task is complete or not, please let me know if there is a way to know the job done to notify user

[@DotNetCoreCentral]

@raj kumar, on job complete you can fire a SignalR message to notify the user.

[@Akustik]

Very useful and well explained. One thing I'm unclear on, why do you AddHostedService() inside Program.cs, rather than Startup.cs? As far as I can tell the method ConfigureServices() is the same.

[@DotNetCoreCentral]

@Akustik, you can use it in Startup, I use it there as I feel since it's a service on its own and running in its own thread, makes it clearer if it is started from the Program class. Again, there is no real technical reason, just my personal coding preference. Hope this answers your question. And thanks for watching!

[@chad9861]

Great video!! Very precise and easy to understand. Thanks for putting such a short video covering bs😃! Just heads up - Going forward in .net6, you can write whole initialization code in classless main with implied using namespace. It also allows old style of using main/startup combo

[@MithunKiet]

Hi my scheduler automatic application is shutting down... Any time please help me

[@DotNetCoreCentral]

@Mithun Kumar, where are you running the application?

[@sleepyinvestorcoder]

Hi, such a great video! if we close the browser the service will stop? if yes. is there a way that even the browser closes the service will continue?

[@DotNetCoreCentral]

@noriel ablana, if you are debugging locally yes it will. But not when deployed in dev/qa/prod. Also, you can configure your Visual Studio not to stop the process on browser close.

[@sleepyinvestorcoder]

@@DotNetCoreCentral I was just testing (in development) and i just thought that it is running even the browser closes, luckily you mentioned here about production, can you teach me how to do that in visual studio? thanks again!

[@ersoyodabas2251]

thank u

[@DotNetCoreCentral]

@Ersoy Odabas, thanks for watching!

[@anantjaisawal8455]

Why you did not created worker service instead of creating a API project?

[@DotNetCoreCentral]

@Anant Jaisawal, the main idea is running the background task part of a service, hence the API Project.

[@c-sharptricks9899]

but in my case job is not repeating its being performed only once, anyone please help

[@DotNetCoreCentral]

@C-Sharp Tricks, can you please share your code in github or somewhere so I can take a look? Thanks

[@microtech2448]

Will this work with IIS idle timeout scenario?

[@DotNetCoreCentral]

@Micro Tech, I have not been using IIS/Windows for more than a few years, all of my services are now in Docker/Linux. Having said that, I know IIS shuts down appdomain if no external HTTP activity. And for that scenario, the only option is to have a periodic health check or ping to keep the server alive. I know it's not an ideal solution, but as far as I know, this is the solution that might work.

[@microtech2448]

@@DotNetCoreCentral so how do you keep background services (which are hosted with .net core api/mvc) all the time active in docker/linux? Doesn't it stop afyer certain time of inactivity like iis? Thanks!

[@DotNetCoreCentral]

@@microtech2448 for .NET Core services running in Linux/Docker hosted in AWS they are always pinged for health check by ECS which keeps it running irrespective.

[@microtech2448]

@@DotNetCoreCentral thanks for the explanation..

[@DotNetCoreCentral]

@@microtech2448 welcome!

[@parko1965]

Background service is killed when api receives no requests after certain amount of time. Not good.

[@DotNetCoreCentral]

@Davey Lad, this should not be the case, if you can share your code I can take a look into what is going on there.

[@parko1965]

@@DotNetCoreCentral I'm publishing to a live webserver and as soon as the app pool's "idle timeout" property is fulfilled the background service is killed.

[@DotNetCoreCentral]

@@parko1965 To be honest I have not been running .NET Core in Windows and IIS for over a year now in Test or Production. I have been using out of the box kestrel web server running in a docker container for Production, and locally using self-hosted in the console. And I have never faced any issue. I think in your case, IIS is shutting down the app. I can try it out on my side and see what can be done with IIS.

[@parko1965]

@@DotNetCoreCentral I have a shared hosting solution and modification of the app pool time out is not an option. I do have a work around but it's not ideal.

[@DotNetCoreCentral]

@@parko1965 I will take a look and see what is the issue with IIS/app pool time out.

[@ashwinikumarshende4777]

Where can i get whole code?

[@DotNetCoreCentral]

@Ashwinikumar Shende, you can get the source code in my GitHub repo here: github.com/choudhurynirjhar/backgroundtask-demo