Coding Shorts: Running Async Jobs in ASP.NET Core

[@heavypeki]

Like as always, concise and straight to the point. You are amazing Shawn. Keep it up.

[@sh00termacg]

Awesome thanks a lot Shawn! Love how concise you are.

[@adamoneil7435]

really cool! I knew Quartz was a thing, but had never seen a demo until now. Love it!

[@swildermuth]

Nice.

[@SamRaddan]

Hey Shawn, can you make a general c# video on streams?

[@PankajNikam]

Thanks for this video :)

[@swildermuth]

My pleasure!

[@palpie]

It was just a small part of this, but you should use ILogger as it is meant to, without string interpolation.

[@swildermuth]

So we should avoid $""? Why?

[@nirajchandrajoshi]

Great video I have one query - can I run a stored proc on crown schedule where that sproc took 20 minutes to complete. And What happen if IIS pool recycles in between while this job is running do I need to reschedule or quartz will take care of this. Please reply.

[@swildermuth]

Look at quartz's durable jobs. Though in the case of a store proc, I might kick it off, not hold a connection the entire time.

[@nirajchandrajoshi]

@@swildermuth Thank you very much

[@alfonsdeda8912]

Hi, great video! What are the advantages over hangfire?

[@swildermuth]

Hangfile requires data storage - there is no non-durable jobs. That's all.

[@PelFox]

How does it keep state if your app crashes / restarts? Can you store the jobs in a queue or database?

[@swildermuth]

You can configure it to store in state (look for Durable and StoreDurably)

[@davood7497]

Coolio !!! 💯💯💯💯💯

[@juanfernandofernandez2730]

First comment

[@swildermuth]

Second!