为什么Visual Studio直到第二次调试会话才达到断点? [英] Why does Visual Studio not hit breakpoint until second debug session?

问题描述

通过TEST菜单或右键单击上下文菜单调试单元测试时，VS2013在将代码更改为当前c#测试类后始终忽略单元测试中的断点.第二次调试会导致断点被击中.

When debugging a unit test through either the TEST menu or the right-click context menu, VS2013 always ignores the breakpoint in the unit test after making a code change to the current c# test class. Debugging a second time causes the breakpoint to be hit.

推荐答案

我怀疑这与VS2013的新功能保持测试执行引擎运行"有关.

My suspicion is that this has to do with VS2013's new feature "Keep Test Execution Engine Running".

您可以通过测试-测试设置"在Visual Studio菜单中切换该功能.

You can toggle that feature in Visual Studio's menu via "TEST - Test Settings".

您还可以通过将RunExsettings文件(将KeepExecutorAliveAfterLegacyRun设置为false)来指定该行为: http://msdn.microsoft.com/en-us/library/vstudio/jj635153.aspx .

You might also be able to specify that behaviour by using a runsettings file with KeepExecutorAliveAfterLegacyRun set to false: http://msdn.microsoft.com/en-us/library/vstudio/jj635153.aspx.

这篇关于为什么Visual Studio直到第二次调试会话才达到断点?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！