Considering a large system with hundreds of assemblies, what is the easiest way to determine which other projects in the large system depend on a specific assembly when there isn't any way to create a single visual studio solution that contains all the projects?
考虑到具有数百个程序集的大型系统，当没有任何方法可以创建包含所有项目的单个visual studio解决方案时，确定大型系统中哪些其他项目依赖于特定程序集的最简单方法是什么？
4 个解决方案
#1
4
I would say that NDepend is the easiest way to determine the dependencies of a .Net Assembly, regardless of complexity:
我会说NDepend是确定.Net程序集依赖关系的最简单方法，无论复杂程度如何：
NDepend is a tool that simplifies managing a complex .NET code base. Architects and developers can analyze code structure, specify design rules, plan massive refactoring, do effective code reviews and master evolution by comparing different versions of the code.
NDepend是一种简化管理复杂.NET代码库的工具。架构师和开发人员可以通过比较不同版本的代码来分析代码结构，指定设计规则，规划大规模重构，进行有效的代码审查和掌握演化。
#2
1
You could use a tool such as ndepend. It will analyze the compiled assemblies and generate a nice graph with arrows pointing to and from your assemblies. I've seen a similar feature in VS2010.
您可以使用ndepend等工具。它将分析已编译的程序集并生成一个带有指向和来自程序集的箭头的漂亮图形。我在VS2010中看到过类似的功能。
#3
0
Configure the operating system to index your source code and search the content for the angle brackets that indicate a reference. Problem is that the path in the reference might be different depending on where the refering projects reside in relation to the one you are looking for so some regular expression might be in order.
配置操作系统以索引源代码，并在内容中搜索指示引用的尖括号。问题是引用中的路径可能会有所不同，具体取决于引用项目相对于您要查找的项目所在的位置，因此某些正则表达式可能是有序的。
#4
0
I'll third the NDepend suggestion, it works extremely well for this problem. You don't have to change anything about your Visual Studio solutions or projects to use it.
我将第三个NDepend建议，它对这个问题非常有效。您无需更改有关Visual Studio解决方案或项目的任何信息即可使用它。
JB
JB
#1
4
I would say that NDepend is the easiest way to determine the dependencies of a .Net Assembly, regardless of complexity:
我会说NDepend是确定.Net程序集依赖关系的最简单方法，无论复杂程度如何：
NDepend is a tool that simplifies managing a complex .NET code base. Architects and developers can analyze code structure, specify design rules, plan massive refactoring, do effective code reviews and master evolution by comparing different versions of the code.
NDepend是一种简化管理复杂.NET代码库的工具。架构师和开发人员可以通过比较不同版本的代码来分析代码结构，指定设计规则，规划大规模重构，进行有效的代码审查和掌握演化。
#2
1
You could use a tool such as ndepend. It will analyze the compiled assemblies and generate a nice graph with arrows pointing to and from your assemblies. I've seen a similar feature in VS2010.
您可以使用ndepend等工具。它将分析已编译的程序集并生成一个带有指向和来自程序集的箭头的漂亮图形。我在VS2010中看到过类似的功能。
#3
0
Configure the operating system to index your source code and search the content for the angle brackets that indicate a reference. Problem is that the path in the reference might be different depending on where the refering projects reside in relation to the one you are looking for so some regular expression might be in order.
配置操作系统以索引源代码，并在内容中搜索指示引用的尖括号。问题是引用中的路径可能会有所不同，具体取决于引用项目相对于您要查找的项目所在的位置，因此某些正则表达式可能是有序的。
#4
0
I'll third the NDepend suggestion, it works extremely well for this problem. You don't have to change anything about your Visual Studio solutions or projects to use it.
我将第三个NDepend建议，它对这个问题非常有效。您无需更改有关Visual Studio解决方案或项目的任何信息即可使用它。
JB
JB