Note that there are some explanatory texts on larger screens.

plurals
  1. POShow Previous Statement while debugging with Visual Studio 2008
    primarykey
    data
    text
    <p>Is it possible to the show the previous statement in the method that I'm debugging with Visual Studio 2008?</p> <p>What I'm currently doing is dragging the yellow arrowhead to the previous statement location or scrolling there and then pressing <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>F10</kbd></p> <p>But with some large methods the current statement might be quite a few lines upwards and it will really speed-up my debugging if I can press a shotcut key to jump to the previously executed statement.</p> <p>I can jump to the previous method using the Call Stack <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>C</kbd> but how do I jump to the previous statement?</p> <p>Edit: This might sound like a stupid question if the method is small, I mean, uhmm, the previous executed statement will probably be right above the currently executed statement, but if it is a large method (I know we should refactor those large methods!) then between the current statement and the previously executed statement might be a couple of lines for example switch or if statements etc. So it takea a few seconds (sorry maybe I'm lazy?) to first scroll back and look for the previously executed statement if I for example want to execute that again.</p> <p>Anyway I think the new <a href="http://blogs.msdn.com/habibh/archive/2009/06/18/an-in-depth-look-at-the-historical-debugger-in-visual-studio-2010-part-i.aspx" rel="nofollow noreferrer">Visual Studio 2010 IntelliTrace (Historical Debugger)</a> might have that functionality, so I'll ave a look at that.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload