PowerShell Action Command Tab
This tab of the PowerShell Action action configures PowerShell options.
Start In: The path that will be the starting directory for the process (optional).
Console file: Loads the specified Windows PowerShell console file (optional).
Input format: Describes the format of data sent to PowerShell.
Output format: Determines how output from PowerShell is formatted.
No logo: Hides the copyright banner.
No profile: Does not use the user profile.
Non-interactive: Does not present an interactive prompt to the user.
Execution policy: Determines which PowerShell scripts (if any) will be allowed to run on your computer (default is Remote Signed):
|•||Default - The execution policy for the PowerShell environment will be used (as configured by the Set-ExecutionPolicy command). To enable PowerShell to execute local unsigned scripts, start PowerShell (running as admin) and enter the command Set-ExecutionPolicy RemoteSigned.|
|•||Restricted - No scripts can be run. Windows PowerShell can be used only in interactive mode.|
|•||All Signed - Only scripts signed by a trusted publisher can be run.|
|•||Remote Signed - Downloaded scripts must be signed by a trusted publisher before they can be run. Use this option when using the Script field on the Command tab.|
|•||Unrestricted - No restrictions; all Windows PowerShell scripts can be run. Use this option for when executing downloaded scripts.|
Show application window: Hides the PowerShell console window when unchecked.
Wait for Completion: When checked, Visual Build waits for the step to finish before continuing and it displays any step output in the Output pane. Uncheck this item to immediately start the next step without waiting for the current step to complete. No output from that step will be shown in Visual Build and if the process is successfully started, it will be treated as a successful.
|•||When this option is unchecked, the process ID of the launched process will be stored in the RUNPROGRAM_PROCESSID temporary macro.|
|•||When this option is checked, the exit code of the process will be stored in the RUNPROGRAM_EXITCODE temporary macro.|
Success exit codes: Visual Build determines the success of the process by examining the exit code of the process. By default, a zero (0) exit code is considered successful, and any other code is a failure. Sometimes, an application will return non-zero exit codes to indicate partial success or additional information, and multiple ranges of success exit codes can be specified in the format low1:hi1, low2:hi2, code3. For instance, 0:5, 10 would cause the values 0 through 5 and 10 to be considered successful exit codes.
File extension: Specifies the file extension to use when creating a temporary file if script code is provided on the Commands tab (optional, uses .ps1 if not specified).
Version: Starts the specified version of PowerShell (optional).
Override default PowerShell executable: Specifies the filename of the PowerShell executable (optional, defaults to powershell if not provided).
Note: To call the 64-bit version of PowerShell from the 32-bit edition of Visual Build, enter a value of %WINDIR%\Sysnative\WindowsPowerShell\v1.0\powershell.exe in this field. To call the 32-bit version of PowerShell from the 64-bit edition of Visual Build, enter a value of %WINDIR%\SysWOW64\WindowsPowerShell\v1.0\powershell.exe in this field.
Additional options: Specifies additional PowerShell flags (optional).