Registering a type as an interface and as self with ASP.NET Core dependency injection
Read OriginalThis technical article addresses a common issue in ASP.NET Core dependency injection: registering a service so it can be resolved both by its interface (e.g., ICustomerService) and its concrete type (e.g., DefaultCustomerService). It explains the problem, the resulting InvalidOperationException, and critiques common workarounds before hinting at a cleaner solution for registering types 'as self'.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
1
Fix your upgrades and migrations with Codemods
Cassidy Williams
•
2 votes
2
Introducing RSC Explorer
Dan Abramov
•
1 votes
3
The Pulse: Cloudflare’s latest outage proves dangers of global configuration changes (again)
The Pragmatic Engineer Gergely Orosz
•
1 votes
4
Fragments Dec 11
Martin Fowler
•
1 votes
5
Adding Type Hints to my Blog
Daniel Feldroy
•
1 votes
6
Refactoring English: Month 12
Michael Lynch
•
1 votes
7
Converting HTTP Header Values To UTF-8 In ColdFusion
Ben Nadel
•
1 votes
8
Pausing a CSS animation with getAnimations()
Cassidy Williams
•
1 votes
9
From Random Forests to RLVR: A Short History of ML/AI Hello Worlds
Sebastian Raschka
•
1 votes
10
You Gotta Push If You Wanna Pull
Gunnar Morling
•
1 votes