No video :(

.NET 7 💥 - Intro to Background Services (Hangfire) with ASP.NET Core Web Api 🔥🔥🔥🔥🔥🔥

Подписаться 25 тыс.

Просмотров 16 тыс.

50% 1

In this video we will be going to learning about How to implement Background Services with Hangfire
Support me on Patreon to access the source code:
/ mohamadlawand
Base App: • .NET 7 💥 - ASP.NET C...
Let us connect:
🌍 My website - mohamadlawand.com
📸 Instagram - / mohamadlawand087
🐦 Twitter - / moe23
♯ Github - github.com/moh...
🎫 LinkedIn - / mlawand
💥 LinkTree - linktr.ee/moha...
Gear I use (affiliate link): amzn.to/3EbT8Jw
Support my work:
/ mohamadlawand
www.buymeacoff...
Hire Me:
transactions.s...
WHO AM I:
I'm Mohamad, a Enterprise Architect working in Manchester, UK. I make videos about web, cloud, desktop and mobile development.
GET IN TOUCH:
If you’d like to talk, I’d love to hear from you. Tweeting @moe23 directly will be the quickest way to get a response, but if your question is very long, feel free to email me at hello@mohamadlawand.com.
#dotnet #hangfire #backgoundservices

Опубликовано:

5 сен 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 20

@djaalabahmed2038 Год назад

I just upload my background job to azure happy to see your video , keep going

@DK-vh5kt 16 дней назад

Thank you for the great video, i was wondering how to add extra parameters or metadata to a job and retrieve the job by them later to perform a schedule ?

@huseyinemecen5508 9 месяцев назад

Hello, I've been working on a project with Hangfire for a while, using an API that I exclusively employ for Hangfire. Within it, I have applications that run hourly, daily, every two hours, etc. I deploy my Hangfire project to IIS and configure all settings in IIS to prevent the application from shutting down. Hangfire works steadily for a certain period, but after a while, I encounter an error on the dashboard saying: "Hangfire - Recurring job can’t be scheduled, see inner exception for details" Triggering the job again makes it continue working, but after a certain time, the same error occurs. This post is open to anyone with relevant knowledge; I'm looking forward to your comments and insights on this matter

@TheAzerue 10 месяцев назад

Please make a video on Continuation job

@StefanSieringer 4 месяца назад

Thank you for the video! In general I have two questions. 1) It is hard to follow what is clientside and what is serverside. When the console is writing that the eMail was sent was this a serverside function? 2) When i do BackgroundJob.Enqueue on clientside with arguments (for example an ID), how can I use it on the server to use it for a method?

@andrei9218 8 месяцев назад

Could you also show a small example of a Continuation job?

@derricardo2521 5 месяцев назад

Nice one! For an beginner it is very hard to understand what is the client and what is the server. Because it is all in the same solution or even method. What are your thoughts?

@JadAbouZaki-px3oo 9 месяцев назад

Thank you

@kek_1459 Год назад

Thank you so much for your job! Can you make a video about mediator notifications?

@andershejgaard3988 8 месяцев назад

Hello Mohamad Nice video. Is it possible to run multiple servers on multiple machines and only have one client/dashboard?

@aliakkawi4759 Год назад

Hi, thanks a lot for your video tutorials. Is it possible to use SignalR for mobile chat applications?

@ben_5466 Год назад

yes

@TheAceInfinity 10 месяцев назад

Hangfire installs Hangfire.Core

@muttBunch 9 месяцев назад

Mohamad, thank you for this nice demo. I have a question though...I'm running a scheduled job every 20 minutes to post logs to SQL. Not sure of any memory leaks, but holy hell, when it started running, memory usage spiked to the full 8gig on my VM. I gave it 16 live, all 16gig is taken, just gave it 24 and now that's almost filled lol. Obviously something funky in my code but WOW on the RAM usage.

@muttBunch 9 месяцев назад

Just noticed that it completed in 7 minutes, but RAM usage is still topped out, not blaming Hangfire but I think I'll comment out the server, re-publish and run the API call that I used in scheduling and see if the RAM usage spikes again.