1, turn on debugging:
In the code editor at the right-click pop-up menu, click Start Debug Debug As
2, a few shortcuts:
F5: with the Step into, usually into the body of the function call trace function, Step Over will not enter the track directly to the call as a statement handle.
F6: Single step Step Over. If you call usually do not care about the details of the statement, single-stepping on it.
F7: Step Return to return to the caller. If you inadvertently Step into a function that does not need to be concerned about, or there is no need for a tracking function, and returns to the caller directly F7 at the statement.
F8: Run to the next breakpoint Resume.
3, several windows:
(1) Variables window
upper right corner of the first window is Variables window, this window is to look at the value of the program variables or objects used (as long as you defined in the program or call the variable will show up here), we can know value of the variable or object is not what you want.
(2) Breakpoints window
upper right corner is the second window Breakpoints window, which is a list of all breakpoints in your program, some breakpoints may be set when you test window through which the previously removed (without having to program which Find).
(3) Expressions window
The third top right corner of the window is the Expressions window, which is somewhat similar to our VS Immediate window, which not only supports the display of the calculation result, the array elements can also display method returns a value. You only need to write an expression you care to come in on it.
(4) Console window
bottom is the console (This window is our common, if not see, then transferred directly from the quick view out to the lower left corner), if there are variable print, in this window you can see the value of this variable output.
