无法使Visual Studio诊断工具正常工作 [英] Can't get Visual Studio Diagnostic Tools to work

问题描述

我在启动Visual Studio 2015(带有Update 3)中的诊断工具时遇到一些问题.我在调试模式"下构建并启动了一个项目，诊断工具"窗口随即弹出

I'm having some problems getting the Diagnostic Tools in Visual Studio 2015 (with Update 3) to start. I build and launch a project in Debug Mode, the Diagnostic Tools window pops up with the text

启动诊断工具...

Starting Diagnostic Tools...

，大约十分钟后，该文本消失，但诊断工具"窗口仍然存在(未显示任何内容).诊断中心也没有输出.在x86和x64平台上都会发生这种情况，以管理员身份运行VS也无济于事.

and after around ten minutes this text disappears but the Diagnostic Tools window remains (with nothing on it). There is no output in the Diagnostics Hub, either. This happens on both x86 and x64 platforms, running VS as administrator doesn't help either.

VShub.exe和Visual Studio标准收集器服务都在运行.

VShub.exe an the Visual Studio Standard Collector Service are both running.

现在它很快就会失败，并且诊断工具"窗口会显示以下消息:

It now fails sooner and the Diagnostic Tools window gives thhe following message:

诊断工具意外失败. 输出"窗口中的诊断中心"输出可能包含其他信息.

The diagnostic tools failed unexpectedly. The Diagnostics Hub output in the Output window may contain additional information.

现在，诊断中心"窗口将显示以下消息:

And now the Diagnostics Hub window has the following message:

VsHub无法找到/启动服务.

VsHub failed to locate/start service.

推荐答案

这是一个环境问题，计算机上运行的软件正在干扰VSHub.exe的正常运行.潜在的问题是，它的运行方式与恶意软件非常相似，将其自身附加到另一个进程(您要调试的程序)，然后使用命名管道与另一个进程(IDE)对话. 无法找到/启动服务"是无法连接命名管道的诊断消息.

This is an environmental problem, software that is running on the machine is interfering with the proper operation of VSHub.exe. Underlying issue is that it operates a lot like malware does, attaching itself to another process (the program you are trying to debug) and then using a named pipe to talk to another process (the IDE). The "failed to locate/start service" is the diagnostic message for not being able to connect the named pipe.

此行为足以引起黑客攻击或触发试图阻止恶意软件执行此操作的软件类型的错误.像Avast，AVG，Sophos，ESET，McAfee之类的产品以前在开发人员的机器上特别不友好，因此已经被确定.尤其需要将Avast选作从未停止过引起麻烦的产品.

This behavior is enough to raise the hackles or trigger a bug in the kind of software that tries to stop malware from doing this. Products like Avast, AVG, Sophos, ESET, McAfee have been identified before for being especially unfriendly on a developer's machine. Avast in particular needs to be singled-out as a product that has never stopped causing trouble.

测试很简单，只需停用产品并检查延迟是否已经消失.您可以通过添加vshub.exe和devenv.exe的特定排除项来li行，但是选择与程序员每天执行的操作更兼容的产品是明智的.我已经看到并亲身经历了Windows随附的反恶意软件解决方案的问题很少.

The test is simple, just de-activate the product and check that the delay is now gone. You might limp along by adding specific exclusions for vshub.exe and devenv.exe, but choosing a product more compatible with what a programmer does every day is wise. I've seen, and personally experienced, very few problems with the antimalware solution included with Windows.

这篇关于无法使Visual Studio诊断工具正常工作的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！