Invoke-Script
PackageDeployment Module Help |
Package Deployment Module |
Invoke-Script Cmdlet |
Version 4.0.0.5 |
Invoke-Script
Synopsis
Run Windows Script
Syntax
Invoke-Script [-ScriptPath] <String> [[-CLRVersion] <String>] [[-Context] <String>] [-ContinueOnError] [-Wow64] [<CommonParameters>]
Description
Use this command to run a Windows script with a scripting engine. The Installer passes the control for running the script to a scripting engine. When the scripting engine is finished running the Windows script, the Installer continues to execute the eScript.
Parameters
-CLRVersion <String> |
||||||
.NET Framework version. |
||||||
|
-Context <String> |
||||||
User: Execution under user account; logging in HKEY_CURRENT_USER, i.e. for the user. |
||||||
|
-ContinueOnError <SwitchParameter> |
||||||
Continues script execution in spite of errors in the respective command |
||||||
|
-ScriptPath <String> |
||||||
Please enter the name of the script file you want to run through a scripting engine. The Installer recognizes the scripting language used by its file extension: VB Script (Visual Basic Script *.vbs), JScript (extended JavaScript *.js), Perl Script (*.pl), PowerShell (*.ps1). |
||||||
|
-Wow64 <SwitchParameter> |
||||||
By default, the PackageDeployment module assumes to run in a 64-bit PowerShell process on 64-bit systems, and therefore defaults to the 64-bit application location (if different from the 32-bit application location) for file and registry accesses. If you want to access the 32-bit counterparts (in the file system %WinDir%\SysWOW64 instead of %WinDir%\System32, in the registry HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node instead of HKEY_LOCAL_MACHINE\SOFTWARE), use the -Wow64 switch. |
||||||
|
<CommonParameters> |
For more information about common parameters, type "Get-Help about_CommonParameters". |