blog/dependency-injection-in-aspnet-core-explained/ #66
Replies: 1 comment 2 replies
-
|
Hello Mukesh, But here I have some confusion, And there are multiple implementations to this like EmailNotification, SmsNotification, AppNotification And how would I go with the DI for this, should i go with Conditional Registrations Can you please clarify with this. And, Can you also clarify with the real use case of an interface, and how this makes the application scalable. |
Beta Was this translation helpful? Give feedback.
-
|
Hey, If you want to send notifications to all channels, you should first register all the services in the DI Container, and use something like the below, This will get a list of all the registered implementations of NotificationService and send notifications via all channels. Is this what you are looking for? The D in SOLID principles will help you understand the answer to your second question. Basically you should aim to build applications that is decoupled. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, Understood the scenario, Thank you for the time 😊. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
blog/dependency-injection-in-aspnet-core-explained/
Dependency Injection (DI) is a foundational concept in ASP.NET Core — and mastering it is key to building clean, testable, and maintainable applications. In this in-depth guide, we’ll break down what DI really is, how it works under the hood in .NET, and how to apply it effectively in both Minimal APIs and Controllers. We’ll cover real-world use cases, interface-driven design, common pitfalls, and advanced patterns like factory delegates and conditional service registration.
https://codewithmukesh.com/blog/dependency-injection-in-aspnet-core-explained/
Beta Was this translation helpful? Give feedback.
All reactions