Revision as of 07:54, 29 June 2012 edit 99.66.145.129 (talk) Removed a bunch of unnecessary text that added no useful information about the topic at hand, included bad grammar and misspellings, and looked to be written just to incite flaming ← Previous edit		Revision as of 23:20, 20 October 2012 edit undo Angrytoast (talk \| contribs) Extended confirmed users 1,196 edits Disambiguated: Linq → Language Integrated Query Next edit →
Line 18: The main shortcoming of the Visual Studio Debugger is its inability to trace into [[kernel (computer science)\|kernel]]-mode code. However, this is possible using a free [[VisualDDK]] extension. Alternatively, kernel-mode debugging of Windows is generally performed by using [[WinDbg]], KD, or [[SoftICE]]. The Visual Studio Debugger also has no ability to debug [[Lambda-expression#Lambda_calculus_and_programming_languages\|Lambda-Expressions]] or [[~~Linq~~Language Integrated Query\|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.

Microsoft Visual Studio Debugger: Difference between revisions