Why avoid captive dependencies in .NET DI?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
A singleton holding a scoped service outlives the scope and uses disposed objects.
WHY — DI instead of guessing?
Why interviewers care about DI:
on DI.
the situation, the default choice, and one exception - that reads as experience.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1A singleton holding a
scoped service outlives the scope and uses disposed objects.
- 2Why it exists
Match lifetimes carefully.
- 3How it works
Captives cause weird production bugs.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
A singleton holding a scoped service outlives the scope and uses disposed objects. Match lifetimes carefully.