Analysing .NET code dependencies–Overview
How can you tell if modules/components in your application are loosely-coupled between each other, and tightly cohesive internally? You could read the code line-by-line, but that becomes difficult once the codebase becomes large.
It can be very valuable to be able to visualise the the dependencies between the various components that make up your application – both at the class and module/assembly level. These tools analyse code, either by parsing the source code, or by analysing the compiled assemblies to produce various summaries and reports about the state of the code.
I’m planning to spend a bit of time in future blog posts reviewing a number of these tools that can help with this analysis, including:
I’m also interested to hear what you use. Let me know in the comments of your experiences with these or other tools I haven’t mentioned.