ASP.Net Core service lifetimes (probably the most practical video you'll ever find)

In this video we dissect ASP.NET Core service lifetimes using a 100% practical approach. We first look into the behavior of the different lifetimes by registering the same service with different lifetimes and checking the output of the service. We then tackle important topics like how ASP.NET Core service lifetimes affect the way we inject services in custom middleware. Last but not least we look into some common errors we could run into when not understanding correctly how service lifetimes are designed to work.
Injecting scoped services into singleton services: • ASP.Net Core: How to i...
#aspnetcore #dependencyInjection #dotnet

[@vaya99]

Best explanation of everything for a Developer - Hats off to you Dan.

[@Codewrinkles]

Glad you found it useful.

[@viniciusmorgado9722]

Thank you for this, a very good video about the topic I finally understand it.

[@Codewrinkles]

I'm glad it was helpful!

[@mamunreza8137]

Very well explained! Thanks a lot 🙂

[@Codewrinkles]

Glad it was helpful!

[@jamesbest2221]

Thank you so much for this! This is my #1 most confusing aspect of asp.net core. Wasn’t sure what to use for web APIs in request response scenarios.

[@Codewrinkles]

I'm glad it was helpful.

[@blasferatu]

This was indeed the best explanation I have seen about service lifetime. Thank you so much for sharing this knowledge. I am looking forward to the next videos targetting the issues raised in this video. I would also like to see a video about how to decide what scope to register a service with. I often feel at a loss on this topic. Thank you.

[@Codewrinkles]

Thank you very much for your feedback. Regarding your question on what scope to register, I don't think it's worth having a video on that topic. Why? Because it's actually based on your needs and according to the described lifetimes. Repositories and data contexts you have to register always as scoped. EF Core does this by default when you do services.AddDbContext();. Loggers and cross-cutting concerns are usually registered as transient as you might need them also outside the scope of a request. You register singleton's when you have a service that kind of keeps track of the app state beyond requests, like analytics, caching and other things like that. If you have more specific questions, please feel free to ask. If I see that the discussion goes a long way, then it might be worth doing a video :)

[@blasferatu]

@@Codewrinkles Thank you!

[@esmaelmohamed8209]

It's well explained also needed more to ⛏️ it in real time project if it's possible. Sir i am sincerely asking for the source code to digest the concept. Respect!!!

[@GameDownloader112]

Well Done!

[@adedoyinphilip8647]

Thank you

[@jkaryskycoo]

YOu should have mroe subscribers

[@lollol-lm9pp]

What do you think about create series ASP.NET Core for total noobs? Those would be interesting? :D

[@Codewrinkles]

I have thought about it, but I'm not sure if there is a real demand on that one, since there are a lot of other channels that do it. I try do to videos on things that I treat differently here then on other channels. But, let's see! Feedback noted! Thanks for dropping a few lines and for watching.

[@lollol-lm9pp]

@@Codewrinkles Can you recommend channel / video tutorial about ASP. CORE? Which you would recommend?

[@Codewrinkles]

I have decided to start one. Lessons will be held as live streams. Will start next week so keep in touch.