Chapter 35
Figure 35-19
Property sheets can inherit from other property sheets, making it possible to build a hierarchy, which makes the tree format for this window very appropriate.
Resource View
The Resource View, only applicable to C++ developers, can be used to navigate the resources that are associated with a particular project, as shown in Figure 35-20. Resources can be edited within Visual Studio 2005 by double-clicking on them from this view.
Figure 35-20
C# and VB.NET applications use the Resources tab on the Project Properties window, which is covered in Chapter 10.
History
A change history for a file that is under source control with Team Foundation Server can be reviewed using the History window, shown in Figure 35-21. Alternatively, a modal dialog is available for those working with another source control provider.
Workspace Control
Figure 35-21
More information on working with source control is available in Chapter 8. This window is only available as part of the Team Suite version of Visual Studio 2005.
Source Control Explorer
In Figure 35-22 the Source Control Explorer appears in the main window. This can be used to navigate the repository built into Team Foundation Server. Files can be checked in and out, versions can be compared, and merge operations can be carried out using this window.
Figure 35-22
More information on the Source Control Explorer is available in Chapter 8. This window is only available as part of the Team Suite version of Visual Studio 2005.
Pending Changes
When a file is checked out of the source control repository, it appears in the Pending Changes window shown in Figure 35-23. This interface can be used to incrementally check files in, roll back changes, or compare the controlled version with the version being worked on.
Figure 35-23
Chapter 35
More information on the Pending Changes window is available in Chapter 8. This window varies between versions of Visual Studio 2005; the Team Suite version, shown here, permits association between pending changes and work items.
Macro Explorer
Figure 35-24 shows the Macro Explorer, which can be used to browse and execute macros. Macros can also be modified by selecting the Edit item from the right-click context menu.
Figure 35-24
Web Browser
Visual Studio 2005 has a built-in web browser, shown in Figure 35-25, that can be used instead of opening another application.
Figure 35-25
Workspace Control
Each .NET language has its own developer center, accessible via the MSDN site at http://msdn.microsoft.com, which provides updates on best practices and information on how to work efficiently with Visual Studio 2005.
Team Explorer
Navigating information held in a Team Foundation Server can be done using the Team Explorer, shown in Figure 35-26. This window provides access to queries that can be used to return work items, available build types, and the source control repository.
Figure 35-26
More information on the Team Explorer is available in Chapter 56. This window is only available after the Team Foundation Client has been installed on top of the Team Suite version of Visual Studio 2005.
Breakpoints
The Breakpoints window is useful for navigating between breakpoints and reviewing any breakpoint conditions. Figure 35-27 shows a breakpoint that will break the fifth time the line of code is executed.
Figure 35-27
More information on the Breakpoints window is available in Chapter 49.
Chapter 35
Immediate
The Immediate window, shown in Figure 35-28, can be used to evaluate expressions without having to run the application. This can be useful if you are unsure of how a method functions or would like to test a method you are currently implementing.
Figure 35-28
More information on the Immediate window is available in Chapter 49.
Script Explorer
Developers who have to work with scripts (JavaScript or VBScript) embedded in their ASP.NET applications can use the Script Explorer, shown in Figure 35-29, to help them navigate and debug their code.
Figure 35-29
More information on the Script Explorer window is available in Chapter 49.
Registers
Figure 35-30 shows the Registers window, which can be used to monitor the values held in the Registers as the application executes.
Figure 35-30
More information on the Registers window is available in Chapter 49.
Workspace Control
Disassembly
The Disassembly window, shown in Figure 35-31, can be used to step through code at a micro level. It is rare to have to debug at this level, but reviewing the execution of the IL statements can reveal performance and other issues that might otherwise have been overlooked.
Figure 35-31
More information on the Disassembly window is available in Chapter 49.
Memory
The Memory window, shown in Figure 35-32, can be used to monitor memory during execution.
Figure 35-32
More information on the Memory window is available in Chapter 49.
Processes
In Figure 35-33, the Processes window displays a list of the processes that the debugger is currently attached to and their state.
Figure 35-33
More information on the Processes window is available in Chapter 49.
Chapter 35
Modules
The Modules window, shown in Figure 35-34, shows which assemblies have been loaded and whether their symbols have also been loaded. In order for the debugger to step into the assembly code, an appropriate symbol file must be located.
Figure 35-34
More information on the Modules window is available in Chapter 49.
Threads
In building a multi-threaded application, it is essential to be able to switch between threads. The Threads window can be used to show the execution point for each running thread (see Figure 35-35). It also displays the priority, name, and ID of each thread.
Figure 35-35
More information on the Threads window is available in Chapter 49.
Call Stack
Figure 35-36 shows the Call Stack window, which can be used to determine a call graph. This can be important when trying to identify the source of an issue. In a multi-threaded application, you can display the call stack for the currently selected thread in the Threads window.
Figure 35-36
More information on the Call Stack window is available in Chapter 49.
Workspace Control
Autos, Locals, and Watch
The multiple Watch windows — which include the Autos, Locals, and a number of additional userconfigurable Watch windows — are used to display the value of variables when the application is in break mode (see Figure 35-37). Nested properties can be navigated by expanding the plus (+) symbol.
Figure 35-37
More information on the Watch windows is available in Chapter 49.
Code Coverage
Testing is a difficult art and being able to determine the percentage of your application that has been tested is nearly impossible. One metric that can be used is how much of your code has been executed — in other words, the code coverage of your test cases. The Code Coverage window shown in Figure 35-38 illustrates a method that is yet to be tested. Other methods are completely covered by the existing test cases.
Figure 35-38
More information on the Code Coverage window is available in Chapters 55 and 56. This window is only available as part of the Team Suite version of Visual Studio 2005.
Test Results
Figure 35-39 shows the Test Results window, which displays the results of the set of tests that were executed. Clicking on any of the results will open a more detailed analysis of the test.
Figure 35-39
Chapter 35
More information on the Test Results window is available in Chapters 55 and 56. This window is only available as part of the Team Suite version of Visual Studio 2005.
Test Manager
The Test Manager, illustrated in Figure 35-40, is used to create a list of tests that can be scheduled or run as a group. This is useful if an application has a large set of tests. A subset of the tests pertaining to the area of the application being worked on can be created so developers can continuously run the tests to ensure they don’t break anything. The full set of tests should also be run as frequently as possible.
Figure 35-40
More information on the Test Manager is available in Chapter 56. This window is only available as part of the Team Suite version of Visual Studio 2005.
Test View
Figure 35-41 shows the Test View window, which can be used to select and run individual test cases.
Figure 35-41
More information on the Test View window is available in Chapters 55 and 56. This window is only available as part of the Team Suite version of Visual Studio 2005.
Team Builds
The Team Builds window (see Figure 35-42) is available only as part of the Team Suite version of Visual Studio 2005.
Workspace Control
Figure 35-42
More information on this window is available in Chapter 56.
Test Runs
Team Foundation Server can be used to schedule a set of tests, perhaps as part of the build process. These test runs can be reviewed using the Test Runs window, shown in Figure 35-43.
Figure 35-43
More information on the Test Runs window is available in Chapter 56. This window is only available as part of the Team Suite version of Visual Studio 2005.
Bookmarks
The Bookmarks window, shown in Figure 35-44, can be used to navigate, enable, and disable bookmarks throughout your code.
Figure 35-44
Data Sources
Figure 35-45 shows the Data Sources window, which is used to generate strongly typed data access code and to provide drag-and-drop support for building data-bound user interfaces.
