> You can't just "go to definition" of the class being injected into yours, even if there is only one. This situation isn't unique when using DI (although admi

> You can't just "go to definition" of the class being injected into yours, even if there is only one. This situation isn't unique when using DI (although admittedly DI does make using interfaces more common). However, that's what the "go to implementation" menu option is for. For a console app, you're right that a DI framework adds a lot of complexity. But for a web app, you've already got all that framework code managing controller construction. If you've got the black box anyways, might as well embrace it.