PowerShell support - Revision history

Bugmenot: /* How to use */ formatting

2016-01-14T09:53:02Z

How to use: formatting

â† Older revision		Revision as of 09:53, 14 January 2016
Line 13:		Line 13:
	== How to use ==		== How to use ==

	Save the script in a file named psexec.nsh, and place it next to your .nsi (or in the NSIS include directory). Then in your script, put an !include psexec.nsh, and call it like this		Save the script in a file named psexec.nsh, and place it next to your .nsi (or in the NSIS include directory). Then in your script, put an <code>!include psexec.nsh</code>, and call it like this

	<highlight-nsis>${PowerShellExec} "echo 'hello powershell'"		<highlight-nsis>${PowerShellExec} "echo 'hello powershell'"

Bugmenot: /* Description */ formatting

2016-01-14T09:51:21Z

Description: formatting

â† Older revision		Revision as of 09:51, 14 January 2016
Line 3:		Line 3:
	== Description ==		== Description ==

	These macros simplify PowerShell use in NSIS, and overcome a bug of PowerShell v2, [[http://forums.winamp.com/showthread.php?p=2969465 described here]], and [[http://connect.microsoft.com/PowerShell/feedback/details/572313/powershell-exe-can-hang-if-stdin-is-redirected reported here]]).		These macros simplify PowerShell use in NSIS, and overcome a bug of PowerShell v2, [http://forums.winamp.com/showthread.php?p=2969465 described here], and [http://connect.microsoft.com/PowerShell/feedback/details/572313/powershell-exe-can-hang-if-stdin-is-redirected reported here]).

	PowerShellExec and PowerShellExecLog respectively place the script output on		PowerShellExec and PowerShellExecLog respectively place the script output on the stack and in the log window.
	the stack and in the log window
	The same goes for PowerShellExecFile and PowerShellExecFileLog, which		The same goes for PowerShellExecFile and PowerShellExecFileLog, which are used to execute a PowerShell script file.
	are used to execute a PowerShell script file.

	If execution fails, the error level is set to 2.		If execution fails, the error level is set to 2.

Bugmenot: /* Pitfalls */ interwikis to Reference/$PLUGINSDIR & :wikipedia:WoW64|

2016-01-13T15:59:49Z

Pitfalls: interwikis to Reference/$PLUGINSDIR & wikipedia:WoW64

â† Older revision		Revision as of 15:59, 13 January 2016
Line 32:		Line 32:
	Be aware that as long as the installer is a 32 bit process, the PowerShell interpreter		Be aware that as long as the installer is a 32 bit process, the PowerShell interpreter
	is also in 32 bit. This can cause redirections in filesystem, registry and environment		is also in 32 bit. This can cause redirections in filesystem, registry and environment
	variables when running or 64 bit systems (see ~~https~~:~~//en.~~wikipedia~~.org/wiki/~~WoW64)		variables when running or 64 bit systems (see [[:wikipedia:WoW64]])

	Also I found that executing a file directly from $PLUGINSDIR caused errors in script execution, and that saving it in a $PLUGINSDIR subfolder prevented the errors.		Also I found that executing a file directly from [[Reference/$PLUGINSDIR\|$PLUGINSDIR]] caused errors in script execution, and that saving it in a [[Reference/$PLUGINSDIR\|$PLUGINSDIR]] subfolder prevented the errors.

	== The Script ==		== The Script ==

CharlesB at 08:22, 8 January 2014

2014-01-08T08:22:58Z

â† Older revision		Revision as of 08:22, 8 January 2014
Line 5:		Line 5:
	These macros simplify PowerShell use in NSIS, and overcome a bug of PowerShell v2, [[http://forums.winamp.com/showthread.php?p=2969465 described here]], and [[http://connect.microsoft.com/PowerShell/feedback/details/572313/powershell-exe-can-hang-if-stdin-is-redirected reported here]]).		These macros simplify PowerShell use in NSIS, and overcome a bug of PowerShell v2, [[http://forums.winamp.com/showthread.php?p=2969465 described here]], and [[http://connect.microsoft.com/PowerShell/feedback/details/572313/powershell-exe-can-hang-if-stdin-is-redirected reported here]]).

	PowerShellExec and PowerShellExecLog respectively the script output on		PowerShellExec and PowerShellExecLog respectively place the script output on
	the stack and in the log window		the stack and in the log window
	The same goes for PowerShellExecFile and PowerShellExecFileLog, which		The same goes for PowerShellExecFile and PowerShellExecFileLog, which

CharlesB at 20:51, 7 January 2014

2014-01-07T20:51:18Z

â† Older revision		Revision as of 20:51, 7 January 2014
Line 3:		Line 3:
	== Description ==		== Description ==

	These macros simplify PowerShell use in NSIS, and ~~overcomes~~ a bug of PowerShell v2, [[http://forums.winamp.com/showthread.php?p=2969465 described here]], and [[http://connect.microsoft.com/PowerShell/feedback/details/572313/powershell-exe-can-hang-if-stdin-is-redirected reported here]]).		These macros simplify PowerShell use in NSIS, and overcome a bug of PowerShell v2, [[http://forums.winamp.com/showthread.php?p=2969465 described here]], and [[http://connect.microsoft.com/PowerShell/feedback/details/572313/powershell-exe-can-hang-if-stdin-is-redirected reported here]]).

	PowerShellExec and PowerShellExecLog respectively the script output on		PowerShellExec and PowerShellExecLog respectively the script output on

CharlesB: fix include

2014-01-07T18:30:45Z

fix include

â† Older revision		Revision as of 18:30, 7 January 2014
Line 40:		Line 40:
	!ifndef PSEXEC_INCLUDED		!ifndef PSEXEC_INCLUDED
	!define PSEXEC_INCLUDED		!define PSEXEC_INCLUDED

	~~!include nsexec.nsh~~

	!macro PowerShellExecMacro PSCommand		!macro PowerShellExecMacro PSCommand

CharlesB: moved Execute PowerShell script or command to PowerShell support

2014-01-07T18:16:22Z

moved Execute PowerShell script or command to PowerShell support

â† Older revision

Revision as of 18:16, 7 January 2014

CharlesB: Initial version

2014-01-07T18:13:35Z

Initial version

New page

{{PageAuthor|CharlesB}}

== Description ==

These macros simplify PowerShell use in NSIS, and overcomes a bug of PowerShell v2, [[http://forums.winamp.com/showthread.php?p=2969465 described here]], and [[http://connect.microsoft.com/PowerShell/feedback/details/572313/powershell-exe-can-hang-if-stdin-is-redirected reported here]]).

PowerShellExec and PowerShellExecLog respectively the script output on
the stack and in the log window
The same goes for PowerShellExecFile and PowerShellExecFileLog, which
are used to execute a PowerShell script file.

If execution fails, the error level is set to 2.

== How to use ==

Save the script in a file named psexec.nsh, and place it next to your .nsi (or in the NSIS include directory). Then in your script, put an !include psexec.nsh, and call it like this

<highlight-nsis>${PowerShellExec} "echo 'hello powershell'"
Pop $R1 ;$R1 is "hello powershell"

InitPluginsDir
SetOutput $PLUGINSDIR\Powershell
File script.ps1
${PowerShellExecFileLog} "$PLUGINSDIR\Powershell\script.ps1" </highlight-nsis>

In your PS commands, remember to escape the dollar sign by doubling it:

<highlight-nsis>${PowerShellExec} "echo $$ProgramFiles"</highlight-nsis>

== Pitfalls ==

Be aware that as long as the installer is a 32 bit process, the PowerShell interpreter
is also in 32 bit. This can cause redirections in filesystem, registry and environment
variables when running or 64 bit systems (see https://en.wikipedia.org/wiki/WoW64)

Also I found that executing a file directly from $PLUGINSDIR caused errors in script execution, and that saving it in a $PLUGINSDIR subfolder prevented the errors.

== The Script ==
<highlight-nsis>
!ifndef PSEXEC_INCLUDED
!define PSEXEC_INCLUDED

!include nsexec.nsh

!macro PowerShellExecMacro PSCommand
InitPluginsDir
;Save command in a temp file
Push $R1
FileOpen $R1 $PLUGINSDIR\tempfile.ps1 w
FileWrite $R1 "${PSCommand}"
FileClose $R1
Pop $R1

!insertmacro PowerShellExecFileMacro "$PLUGINSDIR\tempfile.ps1"
!macroend

!macro PowerShellExecLogMacro PSCommand
InitPluginsDir
;Save command in a temp file
Push $R1
FileOpen $R1 $PLUGINSDIR\tempfile.ps1 w
FileWrite $R1 "${PSCommand}"
FileClose $R1
Pop $R1

!insertmacro PowerShellExecFileLogMacro "$PLUGINSDIR\tempfile.ps1"
!macroend

!macro PowerShellExecFileMacro PSFile
!define PSExecID ${__LINE__}
Push $R0

nsExec::ExecToStack 'powershell -inputformat none -ExecutionPolicy RemoteSigned -File "${PSFile}" '

Pop $R0 ;return value is first on stack
;script output is second on stack, leave on top of it
IntCmp $R0 0 finish_${PSExecID}
SetErrorLevel 2

finish_${PSExecID}:
Exch ;now $R0 on top of stack, followed by script output
Pop $R0
!undef PSExecID
!macroend

!macro PowerShellExecFileLogMacro PSFile
!define PSExecID ${__LINE__}
Push $R0

nsExec::ExecToLog 'powershell -inputformat none -ExecutionPolicy RemoteSigned -File "${PSFile}" '
Pop $R0 ;return value is on stack
IntCmp $R0 0 finish_${PSExecID}
SetErrorLevel 2

finish_${PSExecID}:
Pop $R0
!undef PSExecID
!macroend

!define PowerShellExec `!insertmacro PowerShellExecMacro`
!define PowerShellExecLog `!insertmacro PowerShellExecLogMacro`
!define PowerShellExecFile `!insertmacro PowerShellExecFileMacro`
!define PowerShellExecFileLog `!insertmacro PowerShellExecFileLogMacro`

!endif
</highlight-nsis>

== Version History ==
; [Update 2014-01-07]
: Initial version

[[Category:System Related Functions]]