That would not be a very useful features, since there should hardly be any of your DI configuration written in XML. 99% of the configuration should be done in code. So to do any useful analysis, NDepend should look at the code that configures the DI configuration, but this is actually very hard and to yield any useful analysis, this needs deep knowledge of the DI framework in question. For instance, just look at what the Agent Mulder (https://github.com/hmemcpy/AgentMulder) plug-in for Resharper does. It integrates DI containers with Resharper, but it stops at the point where DI containers get useful: batch registration. So to be honest, I don't think that static analysis is really helpful in this area, since DI containers dynamic in nature and you'll need to run code to be able to analyze what's happening.
Steven
That would not be a very useful features, since there should hardly be any of your DI configuration written in XML. 99% of the configuration should be done in code. So to do any useful analysis, NDepend should look at the code that configures the DI configuration, but this is actually very hard and to yield any useful analysis, this needs deep knowledge of the DI framework in question. For instance, just look at what the Agent Mulder (https://github.com/hmemcpy/AgentMulder) plug-in for Resharper does. It integrates DI containers with Resharper, but it stops at the point where DI containers get useful: batch registration. So to be honest, I don't think that static analysis is really helpful in this area, since DI containers dynamic in nature and you'll need to run code to be able to analyze what's happening.