Manage a Debugging Session in Windows PowerShell ISE

Q

How to manage a Debugging Session in Windows PowerShell ISE?

✍: FYIcenter.com

A

To start debugging - Press F5 or, on the toolbar, click the Run Script icon, or on the Debug menu click Run\/Continue. The script runs until it encounters the first breakpoint. It pauses operation there and highlights the line on which it paused.

To continue debugging - Press F5 or, on the toolbar, click the Run Script icon, or on the Debug menu, click Run\/Continue or, in the Console Pane, type C and then press ENTER. This causes the script to continue running to the next breakpoint or to the end of the script if no further breakpoints are encountered.

To stop debugging - Press SHIFT-F5 or, on the Debug menu, click Stop Debugger, or, in the Console Pane, type Q and then press ENTER.

To Step Into - Executes the current statement and then stops at the next statement. If the current statement is a function or script call, then the debugger steps into that function or script, otherwise it stops at the next statement. Press F11 or, on the Debug menu, click Step Into, or in the Console Pane, type S and press ENTER.

To Step Over - Executes the current statement and then stops at the next statement. If the current statement is a function or script call then the debugger executes the whole function or script, and it stops at the next statement after the function call. Press F10 or, on the Debug menu, click Step Over, or in the Console Pane, type V and press ENTER.

To Step Out - Steps out of the current function and up one level if the function is nested. If in the main body, the script is executed to the end, or to the next breakpoint. The skipped statements are executed, but not stepped through. Press SHIFT+F11, or on the Debug menu, click Step Out, or in the Console Pane, type O and press ENTER.

 

Introduction of Windows PowerShell ISE

⇒⇒Windows PowerShell Tutorials

2016-10-04, 361👍, 0💬