Shelexecute & Transform File

[blumi]

I found here some Syntax like this.

ShellExecuteWait('msiexec', '/L*v "%TEMP%\log.log" /i "install.Msi" TRANSFORMS="install.mst" /qb')

I tried the same but with some variables which contain some paths and names.

$Setup="\\server\path\path\setup.msi"
$Parameter="trans.mst"

ShellExecuteWait('msiexec', '/L ' & @DesktopDir & "\log.log"' /i "' & $Setup & '" TRANSFORMS="'&$Parameter&'" /qb')

Does the tranform Parameter need the path to the file too?

It is in the same directory as the MSI file

Thank you

[Subz]

Usually best practice to put the path in, noticed you're missing a double quote before @DesktopDir.  If your script is going to be in the same directory as the msi, you can use something like this:

Local $sMsiFilePath = @ScriptDir & "\setup.msi"
Local $sTransform = @ScriptDir & "\trans.mst"

RunWait('MsiExec.exe /i "' & $sMsiFilePath & '" TRANSFORMS="' & $sTransform & '" /qb /l "' & @DesktopDir & '\log.log"')

 

[blumi]

21 hours ago, Subz said:

Usually best practice to put the path in, noticed you're missing a double quote before @DesktopDir.  If your script is going to be in the same directory as the msi, you can use something like this:

Local $sMsiFilePath = @ScriptDir & "\setup.msi"
Local $sTransform = @ScriptDir & "\trans.mst"

RunWait('MsiExec.exe /i "' & $sMsiFilePath & '" TRANSFORMS="' & $sTransform & '" /qb /l "' & @DesktopDir & '\log.log"')

 

That works fine, thank you.

Why do you use RunWait instead of ShellexecuteWait?

[Juvigy]

If you dont have MSIExec.exe associated with MSI files Shellexecute will fail. I guess it is that or he just like Run command better