List of Figures

Chapter 1: Strategic Debugging Issues

Figure 1-1: Causes of application failure

Figure 1-2: Causes of unplanned downtime

Chapter 3: The Visual Studio .NET Debugger

Figure 3-1: How the compilers and the Visual Studio debugger work together

Figure 3-2: The Processes dialog window

Figure 3-3: The Attach to Process dialog window

Figure 3-4: The Immediate window during a debugging session

Figure 3-5: Aliasing in the Command window

Figure 3-6: The Output window showing program compilation information

Figure 3-7: Source window maximized using Shift-Alt-Enter

Figure 3-8: Adding a new function breakpoint

Figure 3-9: Adding a function breakpoint to an overloaded class member

Figure 3-10: A breakpoint with a hit count modifier

Figure 3-11: A breakpoint with a conditional expression modifier

Figure 3-12: Using the Breakpoints window

Figure 3-13: Using a Watch window

Figure 3-14: Using the QuickWatch window

Figure 3-15: Using the Locals window

Figure 3-16: Using the Autos window

Figure 3-17: Using the Me window

Figure 3-18: Using the Call Stack window

Figure 3-19: Using the Modules window

Figure 3-20: Using the Disassembly window

Chapter 4: Using the Visual Studio .NET Debugger

Figure 4-1: The General debugging property page

Figure 4-2: The Edit and Continue property page

Figure 4-3: The JIT debugging property page

Figure 4-4: The Native debugging property page

Figure 4-5: The VB Defaults property page

Figure 4-6: The Debug Source Files property page

Figure 4-7: The Debug Symbol Files property page

Figure 4-8: The solution Configuration property page

Figure 4-9: The project Build property page

Figure 4-10: The project Debugging property page

Figure 4-11: The project Optimizations property page

Figure 4-12: The project Build Configuration property page

Figure 4-13: Single-stepping and debugging CIL code with VB .NET source

Chapter 5: Other Debugging Tools

Figure 5-1: Loading and showing the HelloWorld program with the Cordbg debugger

Figure 5-2: Viewing the optimized code call tree

Figure 5-3: Garbage collection for the StringPerfTestOne process

Figure 5-4: ADepends's view of itself

Chapter 7: Windows Forms Debugging

Figure 7-1: User interface for the sort testing application

Figure 7-2: Dialog window showing simple breakpoint properties

Figure 7-3: Using the Me window to examine the current object

Figure 7-4: Debugging with Watch windows and a conditional breakpoint

Figure 7-5: The project start options page

Chapter 8: Web Services Debugging

Figure 8-1: Test Web page for the CurrentTime Web method

Figure 8-2: Processes debugged by Visual Studio during a standard browser test

Figure 8-3: User interface for testing the TimeServer Web service methods

Figure 8-4: Interactions between a Web service and a SOAP client

Figure 8-5: A Web service exception as it appears on the client

Figure 8-6: A Web service custom exception as it appears on the client

Figure 8-7: A Web service exception as it appears on a nonlocal client

Chapter 9: ASP .NET Debugging

Figure 9-1: Enabling DEBUG within IIS for.aspx files

Figure 9-2: Enabling IIS debug authentication

Figure 9-3: Setting ASP .NET temporary folder permissions

Figure 9-4: Internet Explorer's advanced options page

Figure 9-5: An ASP .NET project's Debugging property page

Figure 9-6: The AspNetDebugDemo front page

Figure 9-7: ASP .NET process debugging with Visual Studio

Figure 9-8: The default ASP .NET error page

Figure 9-9: The page-level custom error page

Figure 9-10: The application-level custom error page

Figure 9-11: Showing page-level trace information

Figure 9-12: Showing application-level trace information using trace.axd

Figure 9-13: Showing the detailed trace of a page request

Chapter 10: Windows Services Debugging

Figure 10-1: The ServiceAdmin Web interface for remote control of services

Figure 10-2: Attaching to the ServiceAdmin process for debugging

Chapter 11: VB .Classic Debugging

Figure 11-1: Simple VB .NET user interface for testing a VB 6.0 component

Figure 11-2: Compiling a VB 6.0 component for use from VB .NET

Figure 11-3: VB .NET project with reference to VB 6.0 project

Figure 11-4: Specifying the location of VB 6.0 source code files

Figure 11-5: Simple VB 6.0 user interface for testing a VB .NET component

Figure 11-6: Adding a VB .NET component reference to the VB 6.0 application

Chapter 12: SQL Server Debugging

Figure 12-1: Option to install SQL Server debugging components

Figure 12-2: Using Server Explorer to work with SQL Server

Figure 12-3: Debugging the SalesByCategory stored procedure

Figure 12-4: The user interface for testing SQL debugging

Chapter 13: Error Handling and Exception Management

Figure 13-1: The Exceptions dialog window

Figure 13-2: Showing CLR exceptions in the System.IO namespace

Figure 13-3: The exception thrown dialog window

Figure 13-4: The debugger's unhandled exception dialog window

Figure 13-5: The CLR asks the user whether he or she wants to debug an unhandled exception.

Figure 13-6: A Windows Forms unhandled exception dialog window

Figure 13-7: The .NET exception performance counters

Chapter 14: Debugging Multithreaded Applications

Figure 14-1: A simple multithreaded application

Figure 14-2: An example run of the ThreadSynch application

Figure 14-3: Process deadlock in the ThreadDeadlock application

Figure 14-4: Using the Threads windows to investigate a process deadlock

Figure 14-5: The user interface of the ThreadMonitor application

Figure 14-6: The user interface of the ThreadGui application

Chapter 15: Debugging Distributed Systems

Figure 15-1: Partial failure versus complete failure

Figure 15-2: Choosing the remote debugging transport protocol

Figure 15-3: Visual Studio setup option to install remote debugging

Figure 15-4: Installing native remote debugging only

Figure 15-5: Remote debugging installation instructions

Figure 15-6: The architecture of the HeartbeatMonitor application

Figure 15-7: Running the HeartbeatMonitor application

Figure 15-8: Specifying the remote path for the RemoteMonitor component

Figure 15-9: Manual remote debugging of the RemoteMonitor component