The settings used in this dialog will be remembered for the active text editor whilst it is open in Xamarin Studio. These arguments will be passed to the PowerShell script being run with the debugger. This will open a Debug PowerShell Script dialog where arguments can be specified. To pass arguments when debugging a PowerShell script you can select Debug PowerShell Script… from the Run menu. Immediate WindowĮxpressions and variables can be entered in the immediate window to get or set values.Īs with the Watch Window, entering a PowerShell command with missing parameters will cause the debugger to stop working. The PowerShell file will need to be closed and re-opened before the debugger will work again. Please note that entering a PowerShell command with missing parameters will cause the debugger to stop working. Variables and expressions can be entered in the Watch Window. When debugging the Locals window will show the values of variables grouped by each PowerShell scope – Auto, Local, Script and Global. Printing a message and continuing is not currently supported.īreaking when the value of an expression changes is not currently supported.įunction and exception breakpoints are not currently supported. Due to this restriction the other hit count options may not work as expected. The PowerShell Editor Services debugger supports the ‘When hit count is equal to’. Hit conditions are only partially supported. The Edit Breakpoint dialog says to use a C# boolean expression which is incorrect. Hovering the mouse over a variable will open a tooltip showing the variable value.īreakpoint conditions should use PowerShell syntax and not C# syntax. Once the debugger has started you can select Step Over, Step In, Step Out or Continue Debugging from the Run menu by clicking one of the main toolbar buttons. You can open just a PowerShell script into Xamarin Studio and then run the debugger. Set a breakpoint on a line by clicking in the left hand margin, then select Start Debugging from the Run menu.Īlternatively you can click the Run button in the main toolbar.Ī solution does not need to be open in order for a PowerShell script to be run with the debugger. To debug the currently active PowerShell file open in the text editor, To create a new PowerShell script there is an empty PowerShell file template available from the New File dialog.Īfter creating a new PowerShell file it must be saved before it can be run or debugged. Right clicking on a PowerShell command and selecting Show API Documentation will open the online help for that PowerShell command, if it is available, in the web browser. On typing the new name and the text will be replaced. The references found are then displayed in the window.Ī variable or method can be renamed in the text editor by right clicking and selecting Rename. To find references of a variable or a method you can right click in the text editor and select Find References. Hovering the mouse over the highlighted error will show information about the error. Syntax errors are highlighted in the text editor. Hovering the mouse over a PowerShell command will show a tooltip with information about that command. Code CompletionĪs you type in the text editor you will see code completion for PowerShell variables.Īn overview of PowerShell command parameters when you press the space key after entering a PowerShell command.Ĭode completion for PowerShell command parameters. PowerShell 3 and higher are supported on Windows. PowerShell 6 needs to be installed on Mac and on Linux. The PowerShell addin uses the PowerShell Editor Services which is also used by the PowerShell extension for Visual Studio Code. Xamarin Studio version 6.0 and later now have PowerShell editing and debugging support with a PowerShell addin.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |