Microsoft Visual Studio Debugger: Difference between revisions

Content deleted Content added
JAnDbot (talk | contribs)
No edit summary
Line 4:
More advanced features of the most recent versions of this debugger include:
* Full symbol and source integration.
* '''Edit and continue''' support, enabling source code changeto be modified and recompilationrecompiled on-the-fly without having to restartexit the current running program or restart the debugger (32 bit applications only).
* Attaching and detaching to and from processes.
* Integrated debugging across programs written in both [[Microsoft .NET|.NET]] and native [[Microsoft Windows|Windows]] languages (calls from [[C Sharp (programming language)|C#]] to [[C++]], for example).
* Remote machine debugging.
* Attaching and detaching to and from processes (both on the current machine and a remote machine).
* Integrated debugging across programs written in both [[Microsoft .NET|.NET]] and native [[Microsoft Windows|Windows]] languages (calls from [[C Sharp (programming language)|C#]] to [[C++]], for example).
* Full support for C++, including templates and the standard library
* Debugging [[ASP.NET]] [[Web Service]]s.
* Tracing into DLL code when symbolic debugger information is present.
* Standard as well as more advanced [[breakpoint]] features, including conditional, address, data breakpoints.
* Many ways of viewing program state and data, including multiple watch windows, [[thread (computer science)|threads]], [[call stack]], and modules. The way library and user data types are displayed can be configured (e.g., to show contents of a container class, rather than its raw structure).
* [[Scripting language|Scriptability]] or the ability to control via a macro or scripting language. Any language which can talk to [[Component Object Model|COM]] can be used.
* '''Edit and continue''' support, enabling source code change and recompilation without having to restart the program (32 bit applications only).
* Local and remote debugging of SQL stored procedures on supported versions of Microsoft SQL Server.
 
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]]. 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.
 
[[Category:Debuggers]]