Microsoft Visual Studio Debugger: Difference between revisions

Revision as of 19:05, 15 June 2011

Revision as of 15:10, 17 August 2011

Line 21:

Edit-and-continue is held by many developers as Microsoft's greatest asset given unto developers, as a program that is running in memory with a simple mistake (such as "for (i = 0; i < some_var; i++)" can be converted to its correct form "for (i = 0; i < some_var - 1; i++)" without having to stop the current program or exit the debugger. This feature allows very common mistakes to be corrected easily and with great time savings over other solutions which require exiting the program, making the change, recompiling, and then navigating back through the running program to the previous ___location, including those available by the [[GNU Compiler Collection]] chain and debuggers like [[GDB]] and DBX. Still other developers believe that such "sloppy programming techniques" represent a greater philosophical issue related to the mindset of the developer, and should be addressed in other ways such as "teaching them proper coding techniques." This division over belief systems and coding methodology philosophies often causes staunch debate and even moderate hostility between some of the more zealot in both camps.

Debugger Canvas steppssteps through code in the debugger in Visual Studio Ultimate 2010.

<ref name="Debugger Canvas VS10">{{Cite web

|url= http://blogs.msdn.com/b/somasegar/archive/2011/06/13/debugger-canvas-on-devlabs.aspx