Hello,In a basic MSI, is there a way to access translations strings in a powershell custom action ?I mean accessing the string list defined in InstallShield's 'User interface' section, item 'String editor' (see image below) ?
I run a powershell script when installing my stuff.Is there a way to tell InstallShield 2018 not to run the script when uninstalling ?Or maybe there is a property I can test to avoid execution of the commandlets of my powershell script.
Does any one have an idea why my Basic MSI project tries to copy a file C:\Program Files (x86)\InstallShield\2018\Redist\Language Independent\i386\setup.exe into my target build directory ?I've checked, and the setup.exe file doesn't exist in the Ins...
I have provided a set of support files (DOS batch files). I need to run these script and I intend to do this through a powershell script action.Does anyone know how I can get the path to the support files folder I have declared ?I have tried this wit...
Now this time it worked.In powershell, I use this function to popu dialogs.function error_message([string]$message){
trace-info "ERROR_MESSAGE: $message"
$wshell = New-Object -ComObject Wscript.Shell
$wshell.Popup($message,0,"CT...
I've changed my code and used your suggestion (which by the way did a better job then what I did ).Yet the message popup is still hidden by the InstallShield window.Maybe it's the wrong approach. Is there a way to let install shield display the err...
If I understand this well, I could write something likeif (Get-Property -name REMOVE){# we are uninstalling} elif (Get-Property -name REMOVE) {# we are upgrading} else {# we are installing (from scratch)}
Ok, and is there a way to test a property in the powershell that would make it possible to write something like .$action = Get-Property -name <some property>
switch ( $action){
Installing
{
# do something to install my stuff
}
Uninstallin...
Just before it stopped building, I unchecked two prerequisites !!!For the sake of it, I checked them again (like it was before).And guess what ? It builds again ! It seems to be related to the prerequisite feature. Any idea why ?