Clever Geek Handbook

The easiest way to identify .NET assembly dependencies

Given a large system with hundreds of assemblies, what is the easiest way to determine which other projects in a large system depend on a particular assembly when there is no way to create one visual studio solution containing all the projects

+1


source to share


4 answers


I would say NDepend is the simplest way to define .Net Assembly dependencies , regardless of complexity:



NDepend is a tool that makes it easy to manage a complex .NET database. Architects and developers can analyze code structure, set design rules, plan massive refactorings, perform effective code reviews, and master evolution by comparing different versions of code.

+4


source


You can use a tool like ndepend . It will analyze compiled assemblies and generate a nice graph with arrows pointing to and using your assemblies. I've seen a similar feature in VS2010.



+1


source


Configure the operating system to index the source code and search for content for the angle brackets that indicate the link. The problem is that the path in the link can be different depending on where the referenced projects are in relation to the one you are looking for so that some kind of regex might be ok.

0


source


I'll be the third suggestion of NDepend, it works really well for this problem. You don't need to change anything about your solutions or Visual Studio projects.

JB

0


source






More articles:


All Articles