Cezary Walenciuk Profile picture
Jan 25, 2022 6 tweets 3 min read Read on X
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

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Cezary Walenciuk

Cezary Walenciuk Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @WalenciukC

May 10, 2022
Can you use CQRS pattern without MediatR or reflection ?

You can🤩

C# and dependency injection container is all you need

@oskar_at_net created 2 blog post and gave 2 talks about this. Power and credits to him🤘👨‍🎤

At first you need to create these interfaces. Then👇

#dotnet
Then you create auxiliary extension methods that allow you to easily add Query and Command classes that implement these interfaces to Dependency injection container

Here is the code for AddCommandHandler extension method
Here is the code for AddQueryHandler extension method

We stick to the convention that commands don't return anything. You may not like it ¯\_(ツ)_/¯

Queries obviously return something, so the code for this extension method and interface IQueryHandler is a little different
Read 12 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(