我有一个相当复杂的应用程序，它已经被划分为多个部分。每个组件都有它包含一组项目的解决方案文件。所以我喜欢把它当作一个组件有多个项目/它的DLL。还有一个共同的组成部分。所有其他组件取决于共同。因此，编译是这样的： 恶性component1.compile编译常用，然后编译COMPONENT1因为COMPONENT1依赖于共同。 随着时间的推移共同已经变得相当大。我pretty的确保它可以分割成几个更小的组件。然后，组件需要仅仅依靠其中的一些较小的，打破了共同。这将有望减少编译时间的不同组件。

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?

推荐答案

NDepend的带有一个依赖图再加上相关矩阵。默认情况下，你会得到.NET程序集依赖关系图，并不仅限于只有一个与解决方案组件。 NDepend的是集成在VS 2010年，2008年和2005年，它可以显示任何类型的图形在您的code，包括：

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:

等等...

请参阅screenshoots从这个博客帖子中提取：交互式$ C C $依存关系图表

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