Let's see🤔
How can you control life cycle of injected elements in ASP..NET Core DI Container?
We have three live cycles:
➡️ Singleton
➡️ Scoped
➡️ Transient
How do they work? Here is the thread 🧵👇 with the demo and code
#dotnet #csharp #devcommunity
Do to the demo, we need to create an interface per life cycle option.
An implementation of that interface will return a unique ID.
New ID means that element was recreated
We need a class that will represent a service layer that will be created in Controller.
We need to do this to see how "Scoped" and "Transient" life cycles are working
Here is the Controller
We're going to inject all interfaces🧪
But each interface will have different life cycle according to the name of that interface
In Program.cs we're setting up DI Container and all life cycles
As we can see:
➡️Singleton will always have the same ID. We will never recreate that object
➡️Scoped will have the same ID and object till next request
➡️Transient will always create new object when is needed
See you soon in the next thread about life cycles in Middleware
Share this Scrolly Tale with your friends.
A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.