Windows

Autos Window

displayed from (Debug > Windows > Autos)
Items in this window persist, or maintain their values, only for the current statement or scope. When the program goes on to execute code that does not use the variables (ie they go out of scope) they disappear from the AutosWindow.
This window is automatically populated with variables.
Only available when in break mode
Displays all the variables that are in use in and around the line of code currently being executed.

What is the difference between this is Locals window ??

Command Window

This window can be used to execute commands directly from the editor.
(View > Other Windows > Command Window)
This is always available, not just when in break mode.

Debug.Print sValue 

SS

Using Aliases
This window has a large number of shortcut keys known as aliases that can be used.
? sValue
To see a complete list of all the aliases available type "alias" into the window and press Enter.

You can even create your own by prefixing it with the word alias
> alias <aliasname> <commandName>

To remove an alias type the following
> alias <aliasname> /delete

Error List Window

Code Errors detected by the automatic syntax checker are listed here.
Double clicking on an error takes you straight to the troublesome spot in your code.
You can also use the line number of each error
(Tools > Options > Text Editor > Basic > Line Numbers)

Immediate Window

used at design time
displayed from (Debug > Windows > Immediate)

Can be used to run commands immediately
? sValue
If a variable has not been initialised then Nothing will be displayed as the value in this window.

You can also type formulas and statements

Trace.TraceInformation("some text") //puts text in the immediate window 

It is possible to change the value of variables in the following windows:
Immediate, Watch, Locals, Autos
this means you can test code changes by changing the variable at run-time.

Locals Window

displayed from (Debug > Windows > Local)
Only available when in break-mode
This window works in the same way as the Autos Window in that variables are automatically populated
The main difference is that the Locals window only displays variables that exist in the method that is currently being stepped through
SS of both !!

This does not show string variables that have been assigned a blank string when debugging in release mode as the garbage collection is very efficient

Output Window

displayed from (Debug > Windows > Output)
This displays status information about your solution when it is built.
This will tell you if the build was successful.
If the build fails then the Error List window is displayed (automatically ??)

This window automatically opens when you build a VSTO solution.

Quick Watch Window

Only available when in break mode
This window is similar to the Watch window except that you can only add one variable to this window.
When you are in break-mode you can right click on a variable and select "Quick Watch" to add it to this window.
If you want to see the value on an ongoing basis (??) then you need to add it to the Watch WIndow.

You can also display values by hovering over the variable or statement with the mouse and using the DataTips pop up window.

Watch Window

only displayed at run-time
This is very useful for exaiming the state of variables and properties as they are evaluated by the compiler.
(Debug > ??)
You can add code variables that you want to monitor
You can drag these variables and statements into this window from the code editor.
The current value of these variables and statements is displayed.
As you step through code these values change automatically to reflect there latest values.