I'm not exactly sure what you mean. Doesn't all dependency injection work the way I described?
Without being familiar with the framework, you can't trace your way from the class getting injected into to the configuration, even if you're experienced with the language.
I don't think so. When I've seen it done it's usually not been random values injected (except when those values are secret keys which should absolutely not be stored in code to begin with), it's usually injecting a service. Another class, usually with a name that makes it easy to trace down. Like if you're building an OrderService, that might take as a dependency an IProductService, which would have injected into it the class ProductService (personally, I don't like the Hungarian notation that C# uses, but it's a convention and my preference for sticking to strong conventions for the sake of consistency outweighs my distaste for Hungarian notation). That's easy to find, and in fact your IDE can probably take you straight to it from the OrderService's constructor.
It's easy to imagine a hypothetical way that could lead to problems. But in all the code I've worked with, either that scenario is avoided entirely, or other context makes it absolutely clear which IProductService is being used.
It's an ender chest. It functions like a chest, but the contents are always the same for every chest. So you could for example fill it with stuff in one place, and access the same stuff from another chest at another place
sopuli.xyz
Oldest