What is the easiest way to determine the dependencies of a .NET assembly
Considering a large system with hundreds of assemblies, what is the easiest way to determine which other projects in the large system depend on a specific assembly when there isn't any way to create a single visual studio solution that contains all the projects?
I would say that NDepend is the easiest way to determine the dependencies of a .Net Assembly, regardless of complexity:
NDepend is a tool that simplifies managing a complex .NET code base. Architects and developers can analyze code structure, specify design rules, plan massive refactoring, do effective code reviews and master evolution by comparing different versions of the code.