DI newbie. Should I have hundreds of addtransient<> in startup.cs?

Question

0.00/5 (No votes)

See more:

This is my first .net core application. Dependency Injection is all about not newing up classes in the application, but rather injecting them at one place so that they're easily changeable, right? But I can see that I'm quickly going to have so many (possibly hundreds) of repository services and other being injected into my application. Is this normal?

What I have tried:

Tried nothing, just an observational question.

Posted 26-May-20 3:32am

TheRedEye

Updated 26-May-20 3:43am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

F-ES Sitecore · Accepted Answer · 2020-05-26T03:44:00

DI tries to decouple the interface from the implementation so you can swap classes out, but in the real world that rarely happens. The biggest advantage is to allow unit testing as you can replace things with mocked versions of the services as needed.

As for it being normal to have loads of registrations, yes it is. Some DI frameworks let you do registration by configuration so if you have a bunch of "IMyService" and "MyService" items it can auto marry them up, but from my experience it is generally preferred to explicitly declare the registrations as needed.