Would it be possible to trace constructor injection for impact analysis?

[petepeg]

was running this on some C# projects and noticed it wasn't able to trace dependencies from constructor injection. Would be really nice if it could, most likely difficult to implement.

[rs545837]

Right now the dependency graph picks up references from entity content (method calls, type usage in the body, base classes), but it doesn't trace constructor parameter types as edges.

Would you be open to sharing an example from your project (even anonymized)? Would help us get the edge cases right for C# DI patterns.

[petepeg]

If you need I can take some time to spin up an example(most of my code is proprietary), but it's pretty much the standard pattern in C#. You register a service interface in an application builder than it's injected via the constructor into a class. The registration can include the implementation class or it can let the framework handle that.

[rs545837]

thanks for the description this was useful. Lemme hack a bit on this