Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 4
    This should be added to Wikipedia. Commented Feb 21, 2019 at 13:11
  • 2
    It's now the caller's responsability to instantiate a DbContext - I think this would be responsibility of application's entry point to instantiate all required dependencies. So consumer only need introduce required type as a dependency in own contract. Commented Mar 8, 2019 at 20:34
  • 2
    @Fabio It could be. (In that case the caller's responsibility would to provide the resource that was instantiated at application startup to the method/class being called.) In my example, it isn't, though, because that's not a requirement to explain the concept of dependency injection. Commented Sep 22, 2019 at 5:20
  • 1
    So... DI is taking reponsabilities out of any given class? By the way, some other good examples about dependency can be found here: tutorialsteacher.com/ioc/inversion-of-control Commented Oct 5, 2021 at 13:08
  • 1
    Inversion of Control is another name for Dependency Injection, Not ideal too, but a more operational term. Commented Mar 3 at 14:11