http://weblogs.asp.net/vikram/archive/tags/Historical+Debugger/default.aspxTags: Historical DebuggerenCommunityServer 2007 SP1 (Build: 20510.895)http://weblogs.asp.net/vikram/archive/2009/05/27/historical-debugger-in-visual-studio-2010.aspxWed, 27 May 2009 10:26:00 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:7098722vik20000in0http://weblogs.asp.net/vikram/rsscomments.aspx?PostID=7098722http://weblogs.asp.net/vikram/archive/2009/05/27/historical-debugger-in-visual-studio-2010.aspx#comments<p>Hi,<br><br>In The visual Studio 2010 team System, A new feature called Historical debugger. Normally, when we want to debug an application we always put the breakpoint first and then start the Application or attach some process for debugging. Visual studio 2010 team system is coming with a feature called historical Debugging which allows code execution to be rewound in case the breakpoint was not already present when the error occurred.<br><br>Unlike the debugger of Visual Studio 2008 o before which only record the currently active stack, the historical debugger will record all the event like prior function calls, Method parameter etc(whatever required for debugger) even though there is no breakpoint. This allows the code to be rewound whenever an error occurs.<br><br>One drawback of Historical debugger would be that it will take a lot more time and memory as the historical debugger will be recording all events even if no breakpoint are set.<br>&nbsp;<br>Vikram</p><img src="http://weblogs.asp.net/aggbug.aspx?PostID=7098722" width="1" height="1">visual studioHistorical Debugger