Maarten Balliauw • 8/11/2026

Keyed Services (Named registrations) in .NET Service Provider

Read Original

This article explains the problem of multiple implementations for the same interface in .NET's dependency injection, where the last registration wins by default. It introduces keyed services introduced in .NET 8, which allow attaching a key (string, enum, etc.) to a registration and consuming it with [FromKeyedServices] or by key. It covers registration methods (AddKeyedSingleton, AddKeyedScoped, AddKeyedTransient), factory overloads, and consumption patterns. This solves the ambiguity and improves code clarity and maintainability.

0 comments
#dependency injection #Service Registration #Net 8
Keyed Services (Named registrations) in .NET Service Provider

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
Limit token usage in Microsoft Agent Framework
Jesse Liberty • 1 votes
2
How to Roll Back AI Agents: Incident Response, Circuit Breakers, and Recovery Patterns
Paul Bryant • 1 votes
3
Avoiding Reasoning Model Failures with Microsoft Foundry
Luke Murray • 1 votes
4
When Your AI Agent Lies: Silent LLM Fallbacks
Luke Murray • 1 votes
5
Adding a custom MCP server to Claude and ChatGPT
Simon Willison • 1 votes
6
Testing AI prompts and comparing models with promptfoo
Tim Deschryver • 1 votes
7
Superlogical
Mitchell Hashimoto • 1 votes