Any problem with nesting dependency injection?

Question

Any problem with nesting dependency injection?

esam 6

if my page/controller has a dependency injected by asp.net core , but this dependency have a dependency injected which have a dependency injected.... down to multiple levels for example.
is that the way DI is intended to be used?

any problem? performance?

any alternative approach ?

AgaveJoe 30,126 Reputation points

2022-08-15T17:33:24.857+00:00

but this dependency have a dependency injected which have a dependency injected.... down to multiple levels for example. is that the way DI is intended to be used?

It is very common to have multiple levels of dependency injection. A repository is a good example or any service that calls a data access layer. I've have not run across a situation where I needed more than two levels. I'm sure there is a use case for more than two levels, I just have not run into the need.

any problem? performance?

This question is far to open to answer. What kind of problem? What performance metrics? It would be easier if you provided code that illustrates a problem and with explicit performance metrics.

any alternative approach ?

Alternative like different DI frameworks or alternate like not using DI? An alternate to DI is simply passing a parameter.
esam 6 Reputation points

2022-08-16T15:17:55.877+00:00

asking for alternative is meant as a blanket question, just to make sure i am not missing something obvious like the presence of an alternative DI frameworks for .net core.
thank you.
AgaveJoe 30,126 Reputation points

2022-08-16T17:12:35.34+00:00

something obvious like the presence of an alternative DI frameworks for .net core.

There are several IoC service compatible with .NET Core. Just do a Google search.

https://www.hanselman.com/blog/list-of-net-dependency-injection-containers-ioc
esam 6 Reputation points

2022-08-17T14:07:27.09+00:00

your comment should be the answer to the question.

Your answer

AgaveJoe 30,126 Reputation points

2022-08-15T17:33:24.857+00:00

but this dependency have a dependency injected which have a dependency injected.... down to multiple levels for example. is that the way DI is intended to be used?

It is very common to have multiple levels of dependency injection. A repository is a good example or any service that calls a data access layer. I've have not run across a situation where I needed more than two levels. I'm sure there is a use case for more than two levels, I just have not run into the need.

any problem? performance?

This question is far to open to answer. What kind of problem? What performance metrics? It would be easier if you provided code that illustrates a problem and with explicit performance metrics.

any alternative approach ?

Alternative like different DI frameworks or alternate like not using DI? An alternate to DI is simply passing a parameter.
esam 6 Reputation points

2022-08-16T15:17:55.877+00:00

asking for alternative is meant as a blanket question, just to make sure i am not missing something obvious like the presence of an alternative DI frameworks for .net core.
thank you.
AgaveJoe 30,126 Reputation points

2022-08-16T17:12:35.34+00:00

something obvious like the presence of an alternative DI frameworks for .net core.

There are several IoC service compatible with .NET Core. Just do a Google search.

https://www.hanselman.com/blog/list-of-net-dependency-injection-containers-ioc
esam 6 Reputation points

2022-08-17T14:07:27.09+00:00

your comment should be the answer to the question.

Share via

Any problem with nesting dependency injection?

Your answer