Microsoft Visual Studio Debugger: Difference between revisions

Revision as of 00:14, 25 January 2012

Revision as of 07:54, 29 June 2012

Line 20:

The Visual Studio Debugger also has no ability to debug [[Lambda-expression#Lambda_calculus_and_programming_languages|Lambda-Expressions]] or [[Linq]]. This is because of the high complexity the debugger would grow to. However, most developers working with Lambda expressions are able to visualize the data through the several memory windows.

Edit-and-continue is held by many developers as Microsoft's greatest asset given to developers. A program that is running in memory, that encounters a simple mistake, can be corrected 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 steps 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

|title= Debugger Canvas

|author= S. Somasegar

|publisher= MSDN

|date= 2011-06-13

|accessdate= 2011-06-15}}

</ref>

== References ==