🔥 How to use CancellationToken in ASP.NET Core WebApi

[@TellaTrix]

Wow, Amazing content Saeed. I know what the main problem in my organization project. I have poorly managed all resources. I am going to fix them soon.

[@sa-es-ir]

Best of luck with new fixes, hope it will boost your app, Thanks

[@aaa-pt7lm]

Really good work and valueable share 👍👍

[@sa-es-ir]

Glad you like it

[@rahulsinghishere]

Very Informative, Thanks

[@sa-es-ir]

Glad you like it 🌷

[@philskay8724]

A lot of knowledge here, Thanks

[@sa-es-ir]

My pleasure and please help me to share it with your network.

[@fabrizziocht]

Great explanation, thank you!

[@sa-es-ir]

Glad you like it

[@saddamhossaindotnet]

I am very excited man! Already Subscribed. :)

[@sa-es-ir]

Awesome! Thank you!

[@Arasaik]

Hey Saeed, This video was so helpful. Keep going. Please create a video on how to make an asynchronous HttpRequest.

[@sa-es-ir]

Thanks for the feedback, sure I'll do

[@rezabayat9222]

great Saeed. there is one missing part: when to use CancellationToken.None. sometimes we have multiple operations, in which all of them accept cancellationToken; but after specific operation we should not cancel the process. for example: var transfer = service1.GetTransfer(cancellationToken); service2.DoTransfer(transfer, someArgs, cancellationToken); service3.TransferApplied(transer, CancellationToken.None); if we pass the cancellationToken to the third service, if the request is cancelled, we would have an inconsistent state. sometimes we should pass CancellationToken.None, if we want that our code continues running, even if the request is cancelled by the user , timeout, etc.

[@sa-es-ir]

Great input Reza and totally agree, actually it depends on sepecfic requirements but in such cases for keeping task running maybe we don't need to use CancellationToken at all.

[@rezabayat9222]

You are completely right. But there ist one problem: when you do not pass the cancellation token parameter, other programmers may see warnings or later on want to improve the code and add the cancellation token. So to avoid such cases, we can pass the None, to say that it was a known issue.

[@rezakamrani4440]

Just Keep Going!

[@sa-es-ir]

Thanks Kamrani jun❤️

[@smc_onetwo]

should we be using the cancellation token on POST and UPDATE requests?

[@sa-es-ir]

Yes everywhere! For Post or update requests, its more important to use CancellationToken because in any exceptions those changes can be rolled back.

[@thecodeman_]

Keep going!

[@sa-es-ir]

Thank you Stefan, I'll do❤

[@ishfaqbabar1192]

Will it work only on webServer (Kestrel) or it will also work on Out-of-process hosting (IIS) or In-process hosting (IIS)?

[@sa-es-ir]

Works with all webservers including IIS as well.

[@JohnSmith-yr7ih]

Please zoom your IDE, it is difficult to watch with phone, and please provide code, direct link of project for every tutorial.

[@sa-es-ir]

Appreciate for the feedback, very true, I try to keep them in mind for the next video

[@muttBunch]

Saeed, this is awesome. Thank you. Is there anyway to send a cancellation via another endpoint to cancel? I made a live log monitor which runs a while loop looking for !token.IsCancellationRequested, but when it’s running, I’d like to send like a stop parameter to it from another action result. It’s cool that we have Swagger, Postman, etc but in a real world app, obviously the user won’t be interfacing with either of those. Thanks.

[@sa-es-ir]

Happy you like it. About the question, the CancellationToken in automatically createe by webServer (Kestrel) so doesn't make sense to CancellationToken to another request and won't work but if the purpose is only cancelling the second request you can disconnect or abort that request (so the other side will be cancelled)

[@heribertodejesusdejesus8316]

Muchas gracias por la aportación, me has dado mejor visión del uso adecuado del CancellationToken, será interesante ponerlo en práctica. Por otro lado, en el video muestras el ejemplo de la capa de repositorio por EF, sin embargo, si el escenario fuera que para esta capa la comunicación es por StoreProcedures donde para "delete, insert o update " manejan sus propias transacciones, ¿sería recomendable el uso del CancellationToken?

[@sa-es-ir]

It's recommended to use CancellationToken if the method accept it, usually all methods that has "Async" postfix they accept it. In case of stored procedure it's the same and CancellationToken should used as well as it will be cancelled on database

[@heribertodejesusdejesus8316]

Agradezco tu tiempo y pronta respuesta, ya me suscribí a tu canal, excelente día.

[@shreypaidhungat6280]

Subscribed :)

[@sa-es-ir]

Thank you🌷

[@cleitoncarlospereira2006]

Hey Saeed, This video was so helpful. Keep going. Please create a video on how to make an asynchronous HttpRequest.

[@sa-es-ir]

Very glad you like it, Sure it's on my list, stay tuned :)