This question already has an answer here:
- .NET Dependency Management Systems 2 answers
We have a big and complex application composed by at least 700 DLL. The number is growing month after month. The code is not well structured because every DLL is a stand alone solutions. As you can imagine, when have some problem when we have to test a new feature on a DLL because we do not know exactly where it is used.
I am thinking to write a program that scan the file system, open the solution XML file and create a graph that contain all the references.
Is it a good idea?
Do you have some other solutions?