ASP.NET Core Web API .NET 8 2024 - 9. Async/Await

[@tarekabiramia913]

The reason why Delete() does not allow await is: - It does not involve any immediate database interaction when called, merely a state change in memory - does not involve waiting and is a quick in-memory operation, making it asynchronous would not provide any benefits and could even lead to less efficient resource utilization. Thank you for this amazing content, + leaving a question at the end is a good idea it make us dig more into .NET tricks, keep up the good work

[@TeddySmithDev]

sweet thanks for commenting!

[@chiennguyen-in9iz]

and it also happened to the Update() method too, Is It because of the same reason? Thanks.

[@ronjohnson123]

all it took was one teddy video and i instantly understood async & how to implement it, awesome video.

[@TeddySmithDev]

Thanks for watching 👍

[@antoniofuller2331]

Teddy is going DEEP ;-)

[@maheshtamang6158]

this video was so concise and easy to understand! once again thankyou Teddy for this gem series!

[@tomasmichek5842]

Awsome video! I love this tutorial series! One detail I noticed - I think you forgot to change the return value in the GET function that returns all the stocks, it should be the new variable 'stockDto' I believe. That's why the request returned the comments as well.

[@elberghaswe2761]

Remove is not an I/O operation it's just a mark on the DB to delete something you want to delete. then you have SaveChangesAsync wich it's a real I/O operation and this really delete the id from the DB. Even if you use "remove" you can still use your marked data until u use the savechangesasync method. Anyway nice video!!!

[@TeddySmithDev]

🙌👏

[@serfirazabd]

at 5:47 why we did not change the return. should not it be "return Ok(stockDTO);" instead of "return Ok(stocks);" ?

[@TeddySmithDev]

Yes, i actually missed this part and correct in later video. Amazing you noticed that lol.

[@caseyspaulding]

Yes. async await. Good one. Thanks Teddy

[@RajVadla]

Your .NET Series videos are Practical! Thanks man!

[@_jeff.medeiros]

Dude you're a legend

[@TeddySmithDev]

Thanks Jeff!!

[@lukasbarbagallo4767]

the async await keywords is neat syntax allowing concurrency. C# did not invent concurrency or the ability to boost performance of software by utilizing concurrency. However C# came up with syntax which made concurrent programming more accessible, a keyword/syntax pattern which has later been adopted by many popular langs eg python and js. awesome vids! learning a lot

[@TeddySmithDev]

Nice troll attempt lmao

[@lukasbarbagallo4767]

@@TeddySmithDev even better troll attempt

[@MihoubAhmed1]

Remove() method is not a time-consuming operation whereas it only changes a simple state in tracker, while the other counterparts e.g. Find() need to ping the Database which would be a time-consuming process.

[@paskostipandzija4568]

For me aysinc was invented way earlier like in c drivers. Great video

[@yahyo_bey]

why Remove is not async? Because Remove is quick operation. Removing an object is very simple and fast operation, it doesn't involve waiting any external resources db call, making network calls, and reding from disk

[@DarlingtonAzramShoniwa]

Thank you Teddy

[@jasminemerchant3167]

short and crisp :)

[@roshanthapa25]

Async/Await looks piece of cake after watching this series.

[@andreashadjithoma7278]

Thank you for the great content! I assume that we can use *Add* instead of *AddAsync* because according to Microsoft: _"This method is async only to allow special value generators, such as the one used by 'Microsoft.EntityFrameworkCore.Metadata.SqlServerValueGenerationStrategy.SequenceHiLo', to access the database asynchronously. For all other cases the non async method should be used."_ As far as I noticed we are not using sequences right?

[@kvelez]

Perfect.

[@PlayCode_WithMe]

I wish that you were working on visual studio(purple one)

[@mbawuikestanley6930]

When you implemented async, why does the GetAllStock endpoint still returning everything including comments

[@TeddySmithDev]

I noticed this yesterday. I passed in stock instead of stockDto to Ok() (Line 28 + 30) StockController.

[@madoha8641]

Teddy, why are you re-uploading your videos or updating them?

[@TeddySmithDev]

dunno, just bored and want to re-do my old video + make them better

[@madoha8641]

is it worth waiting and watching the updated videos or does it not matter if I continue with the old ones@@TeddySmithDev

[@TeddySmithDev]

Old videos are fine and still relevant. People are still completing them now and getting hired 👍

[@antoniofuller2331]

​@@TeddySmithDev is this an old video???

[@maxiphobos]

Maybe EF repository Delete isn't async to avoid (prevent) other async code manipulating with deleting entity in the same method. It's hard to predict when the async function will finalize its work, so it might be the situation when another function manipulates an entity which hasn't yet been deleted because of the async method work but will be deleted soon.

[@TeddySmithDev]

Yeah plus can’t really come back from a delete too lol

[@AndrewBerry-uo3hy]

you are a goat brother

[@kitesalet]

i got banned from your discord server and i dont know why, it was months ago

[@TeddySmithDev]

I shut discord down. Took way too much time to manage.

[@alucard4974]

C# didn't invent async. "C# takes inspiration on async worflows in F#"

[@antoniofuller2331]

Stop hating dummy, C# invented it. F# only had the workflows