用于评估 IoC 重构代码库中易失依赖关系的工具
我正在尝试重构大型代码库以使用 StructureMap。有谁知道是否有一个工具可以快速扫描代码库并报告 易失依赖项？当然，我总是可以在所有文件中搜索“new”一词，但这也会找到非易失性依赖项，例如 BCL 中使用的不重要的依赖项。我认为 NDepend 可以间接提供一些关于耦合程度的报告，而这正是我希望间接消除的耦合程度。我只是想知道是否有一些专门设计用于协助迁移到使用 IoC 容器的工具。
I'm attempting to refactor a large codebase to use StructureMap. Does anyone know if there's a tool to quickly scan a codebase and report the number of volatile dependencies within classes? Sure, I could always search all files for the word "new", but this would also find non-volatile dependencies such as those used from BCL which are not material. I suppose that NDepend could, indirectly, provide some report on the degree of coupling which, is, indirectly, what I'm looking to eliminate. I'm just wondering if there was some tool that was specifically designed for the purpose of assisting with the migration towards the use of an IoC container.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我不知道有这样的事情。我认为编写一个工具来识别易失性依赖项是相当困难的，因为它们可能与文件 IO 调用到数据库调用一样多种多样。此外，许多开发人员在不同的地方划定了 volatile 和 not 之间的界限。有些人会说 System.Configuration 是不稳定的，另一些人则认为它不是......
I am not aware of anything like that. I think it would be quite hard to write a tool to identify volatile dependencies since they could be as diverse as file IO calls to database calls. Also, many developers draw the line between volatile and not in different places. Some would say System.Configuration is volatile, others would argue it is not...