Visual Studio 2017 中的调试问题
在调试模式下启动我的项目时，我收到以下错误并且必须停止调试:
When starting my project in debug mode, I get the following error and have to stop debugging:
这是错误信息:
评估函数Microsoft.VisualStudio.Debugger.Runtime.Tracing.Refresh"超时，需要以不安全的方式中止.这可能会破坏目标进程如果问题经常发生，请考虑禁用工具 > 选项，设置调试 > 常规 > 启用属性评估和其他隐式函数调用，或更改代码以禁用此方法的评估.有关执行此操作的信息，请参阅帮助.
Evaluating the function 'Microsoft.VisualStudio.Debugger.Runtime.Tracing.Refresh' timed out and needed to be aborted in an unsafe way. This may have currupted the target process If the Problem happens regularly, consider disabling the Tools > Options, setting Debugging > General > Enable property evaluation and other implicit function calls, or change the code to disable evaluation of this method. See help for information on doing this.
我也在 Visual Studio 2017 版本 15.7.0 中看到此问题中的错误消息.原始海报没有说明涉及哪个工作室版本.
I was also seeing the error message in this question with Visual Studio 2017 Version 15.7.0. The original poster doesn't say what studio version was involved.
我在另一个网站上发现了这个有限的帖子:https://www.devexpress.com/Support/Center/Question/Details/T581002/evaluation-of-service-timed-out-and-needed-to-be-aborted-不安全的方式
I found this limited post on another site: https://www.devexpress.com/Support/Center/Question/Details/T581002/evaluation-of-service-timed-out-and-needed-to-be-aborted-in-an-unsafe-way
那篇文章是关于 17.2.3 版的，但除了升级似乎修复"了这个问题，没有其他细节，遗憾的是没有提供升级版本.
That post was regarding version 17.2.3 but there's not details other than an upgrade seemed to have "fixed" the issue and sadly the upgrade version isn't supplied.
我已经从 15.7.0 升级到 15.8.1，情况有所不同.首先，错误消息发生了变化，其次，对我来说，我现在可以继续调试和运行我的程序.之前系统状态一团糟，无法继续运行/调试，我的程序处于奇怪的挂起状态.
I've upgraded from 15.7.0 to 15.8.1 and the situation is different. First the error message has changed and second, for me, I can now continue to debug and run my program. Previously the state of the system was messed up and I couldn't continue running / debugging, my program was in a strange hung state.
新的错误消息文本:为了在评估函数Microsoft.VisualStudio.Debugger.Runtime.Tracing.Refresh"时防止不安全的中止，所有线程都被允许运行.这可能改变了进程的状态，遇到的任何断点都已被跳过.