This web site uses cookies. By using the site you accept the cookie policy.This message is for compliance with the UK ICO law.

<< Previous | 1 | 2 | 3 | Next >> |
Viewing Return ValuesViewing Return Values
When debugging code that calls methods with return values, it is very useful to be able to quickly determine the values generated. Visual Studio makes this very simple using the Autos pane or the immediate window.
Debugging Just My CodeDebugging Just My Code
Visual Studio includes an option that prevents the debugger from stepping through certain code. This simplifies the debugging process by allowing the programmer to concentrate on their own code, rather than that which was generated automatically.
Marking Non-User CodeMarking Non-User Code
Visual Studio's debugger considers several variables when determining how to step through code and react to breakpoints. One such item is code that has been flagged as non-user code. This is automatically stepped over and excluded from the call stack display.
Linking Breakpoints in Visual StudioLinking Breakpoints in Visual Studio
Breakpoints are useful tools for debugging code. They allow the code to be halted at a specific position so that variables can be examined. Visual Studio does not provide a way to make one breakpoint dependent upon another but this is possible.
Hiding Code from the DebuggerHiding Code from the Debugger
Sometimes stepping through properties and methods gives no benefit to a developer who is trying to debug some software. In these situations it can be useful to hide code from the debugger so that it is stepped over automatically.
Automatic Property and Operator Step-OverAutomatic Property and Operator Step-Over
Properties and custom operators generally perform simple tasks that rarely require debugger support. Visual Studio can be configured to automatically step over these items, rather than stepping into them during debugging.
Visual Studio 2010 Parallel Tasks WindowVisual Studio 2010 Parallel Tasks Window
Debugging code that uses parallel programming techniques presents additional difficulties to debugging software that executes on a single thread. Visual Studio provides tools that assist with these problems. One such tool is the Parallel Tasks window.
Using the DebuggerBrowsable AttributeUsing the DebuggerBrowsable Attribute
Visual Studio's debugging windows and tools allow you to examine in-scope objects and the values contained within their properties, indexers and fields. When this is undesirable, a class may change the way in which its debugging information is provided.
Visual Studio Call Stack WindowVisual Studio Call Stack Window
The call stack records each member call, allowing the calling code to be resumed when a member exits. The Call Stack window is a debugging tool in Visual Studio that allows the call stack to be examined whilst a program is in debug mode.
Tracing to Event LogsTracing to Event Logs
Using tracing within an application allows its activities to be logged and reviewed later to assist with identifying and resolving bugs. Messages can be sent to various locations, including Windows event logs that can be examined using the Event Viewer.
<< Previous | 1 | 2 | 3 | Next >> |