Why does Visual Studio not hit breakpoint until second debug session?

Question

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

Answer 1

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

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

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.