How do I get a diagram of the dependencies between my C# projects

Question

I have a fairly complex application which has been broken up into multiple components. Each component has a solution file which contains a bunch of projects. So I like to think of this as a component has multiple projects/dlls in it. There is also a "common" component. All the other components depend on "common". So a compile goes like this: "nant component1.compile" will compile "common" and then compile component1 since component1 depends on "common". Over time "common" has become quite big. I'm pretty sure it can be split into a few smaller components. Then components need to depend only on some of these smaller, broken up "common". This would hopefully cut down on compile time for the different components.

So question: I'd like to visualise the dependency between all the different projects in the application while also tagging which component the project belongs to. How would you do this?

Answer 1

I'd try importing it into a UML tool that could render the dependency diagram between modules for me.

There are several on the market, both commercial and open source. Get the one that gives you the most capability for your budget.

Answer 2

understand was suggested to me this morning (:

http://www.scitools.com/

but honestly i cannot give a proper report on it, since it is too expensive for me...

Answer 3

You could have a look at NDepend : http://www.ndepend.com/

edit to add:

Patrick Smacchia, lead developer of NDepend, blogs here: http://codebetter.com/blogs/patricksmacchia/default.aspx and has written much on the subject of componentisation, which you may find useful.

Answer 4

If you are OK with assembly level information then you should look at Graph add-in to a popular tool Reflector. It provides assembly & class level dependency graph.

Answer 5

Have a look at my free DSM plugin for .NET Reflector downloadable from http://tcdev.free.fr

It allows two different views on your dependencies : a deployment model to find the dependencies between assemblies and an architectural model to show dependencies between types.

If it does not provide visually the information your looking for, you can save the model to xml and run your own script on the data.

The advantage of a dependency matrix is that its much more easier to analyse dependencies visually than box and line graphs

If you need more help let me now

Answer 6

If you have access to Visual Studio 2010 Ultimate, you can select Generate Dependency Graph from the Architecture menu.

There is a walkthrough on MSDN: How to: Generate Dependency Graphs for .NET Code

Answer 7

NDepend comes with a dependency graph coupled with a dependency matrix. By default you'll get a dependency graph of .NET assemblies and it is not restricted to assemblies of only one VS solution. NDepend is integrated in VS 2010, 2008 and 2005 and it can shows any kind of graph on your code including:

• dependencies between assemblies
• method calling graph,
• dependencies of namespaces inside a VS project,
• dependencies of types inside a namespace,
• classes inheritance graph,
• graph representing classes coupling between 2 components

etc...

See screenshoots extracted from this blog post: Interactive Code Dependencies Graph