情迷接口依赖 [英] Discovering Interface Dependencies

问题描述

我已接手维护一个非常大（> 2M SLOC）软件项目，全部用C＃编写的。很少有文档。我现在想做出改变到具有公共接口（约400）的模块，但我不知道什么是所有其它模块（大约有50个）的解决方案可能是使用这个公共接口。

I have taken over maintenance of a very large (>2M SLOC) software project, all written in C#. There is very little documentation. I am now wanting to make a change to a module that has public interfaces (about 400), but I don't know what all other modules (there are about 50 total) in the solution may be using this public interface.

你会如何创建一个局面的接口使用依赖树像这样？该代码库太大，只需导航工程资源管理器和读取源代码。有什么工具或方法用于创建这种类型的依赖分析树？

How would you create an interface dependency usage tree for a situation such as this? The codebase is too big to simply navigate the Project Explorer and read source code. What tools or methods have you used to create this type of dependency analysis tree?

我不希望购买任何工具。在Visual Studio工具，如类视图似乎并没有处理这种规模的项目非常好。我曾经想过写我自己的SED / AWK / Perl的十岁上下的脚本，只是走的源代码，并使用模式匹配来建立自己的依赖性/接口useage数据库，但我不想做一些硬的方式，如果有一个简单的方法。

I do not want to purchase any tools. The Visual Studio tools such as Class View don't seem to handle a project of this size very well. I have thought about writing my own sed/awk/perl-ish script that simply walks the source code and uses pattern matching to build my own dependency/interface useage database, but I don't want to do something the hard way if there is an easy way.

谢谢！

推荐答案

您或许应该买东西如 NDepend的。

如果有另一种免费的工具，将提供类似的价值，我会推荐它。不过，我真的相信NDepend的是你最好的选择。与大小的代码库，它不会需要很长时间的售价$ 400美元的工具来收回成本。

If there was another FREE tool that would provide similar value, I'd recommend it. However, I truly believe NDepend is your best bet. With a code base of that size, it won't take long for a $400 tool to pay for itself.

这篇关于情迷接口依赖的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！