如何阻止 NCover 劫持每个 .NET 程序集？
我知道，严格来说，这不是一个编程问题，但我认为唯一能回答它的人是程序员。
我以前从未发生过这种情况，但在我安装了 Ncover 的一台工作站上，它似乎拦截了我加载的每个 .NET 程序集。例如，安装后，突然需要几分钟才能加载任何 .NET 应用程序； .NET 服务因超时而无法启动； Ncover 本身甚至需要几分钟才能加载。
这是怎么回事？我打开 Process Explorer 查看其中的一些程序集，发现我的程序集引用了 NCover DLL 等，尤其是与 mscorlib 相关的程序集。
以前有人发生过这种情况吗？我不知所措。
I know that this, strictly speaking, is not a programming question, but I think the only people who can answer it are programmers.
I've never had this happen before, but on one workstation where I have NCover installed, it seems to be intercepting every .NET assembly I load. For example, after installing it, suddenly it takes several minutes to load any .NET application; .NET services fail to start because they time out; NCover itself even takes minutes to load.
What's going on here? I opened Process Explorer to look at some of these and found that my assemblies were referring to NCover DLLs and such, especially pertaining to mscorlib.
Has anyone had this happen before? I'm at a loss.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在 IIS 或服务上运行覆盖后，事情似乎没有得到正确清理。查看注册表中的 HKLM\SYSTEM\CurrentControlSet\Control\SessionManager\Environment。如果 Cor_Enable_Profiling 和 Cor_Profiler 作为键存在，您将需要删除它们。此外，您还需要删除 NCover_Pid、NCover_Admin、COMPLUS_ProfAPI_ProfilerCompatibilitySetting、NCover_Process_Module 和 NCover_All（如果存在）。
Looks like things didn't get cleaned up correctly after running coverage on IIS or a service. Check out HKLM\SYSTEM\CurrentControlSet\Control\SessionManager\Environment in your registry. If Cor_Enable_Profiling and Cor_Profiler are there as keys, you're going to want to delete them. Also, you'll want to delete NCover_Pid, NCover_Admin, COMPLUS_ProfAPI_ProfilerCompatibilitySetting, NCover_Process_Module, and NCover_All if they're there.