Hi, did you fix this issue? I am experiencing same issue with InstallScript MSI. ... View more

Agshah, Your observation is correct. I just tested the behavior of setting and retrieving  a public property and I see the same behavior.  However, the global property (the flag) can be set in  function OnFirstUIBefore() and be used in Custom Actions. In my project, I set a global property (a flag) a new value in the OnFirstUIBefore(), then I use this flag as the condition to drive the behavior of a Custom Action. This approach worked for me. There are quite a lot of types for defining Custom Actions  such as SetDirectory, SetProperty, calling functions from VBScript and etc. I am thinking that the SetProperty custom action might be meant to set a new value to a Global Property session wide but I did not try it. You may explore the Custom Actions to see if you can get what you desired functionality done. ... View more

Hi @agshah ,   Can you try with sample rul file given in InstallShield's INSTALLDIR for an eg:C:\Program Files (x86)\InstallShield\2019\Script\Isrt\src\ISRTScriptDialogs.rul which has SdWelcome function defined? There you can add check for property like IS_MAJOR_UPGRADE present or not using MsiGetProperty.If that doesn't help you can add productversion based check just to check this is major upgrade of previous setup. Pseudo code would be:   #define TXTBOX 1301 //CONTROL identifier .......   function SdWelcome(szTitle, szMsg) string  svName; number nSize; HWND hwndDlg,hwndTxtBox; ..... ... hwndTxtBox = GetDlgItem(hwndDlg,TXTBOX); nSize=256; MsiGetProperty(ISMSI_HANDLE,"ProductVersion",svName,nSize); if(svName=="2.00.0000") then _WinSubShowWindow(hwndTxtBox,1); _WinSubEnableControl(hwndDlg,TXTBOX,1); else _WinSubShowWindow(hwndTxtBox,0); _WinSubEnableControl(hwndDlg,TXTBOX,0); endif; end You can find the same in attached sample .rul file as well.   Thanks, Jenifer ... View more

agshah wrote: Hi all, I created a custom action of type Error. In this custom action for 'Error Message' I am specifying a property. e.g. [MYERR_MSG] MYERR_MSG is a translatable property set to a string in string editor whose value is : %P is already installed. When the custom action gets execute the error message displayed is "%P is already installed." %P does not get replaced by product name. How do I get it to be replaced by product name at runtime. thanks. Hi To set error message ,try setting it like [PRODUCTNAME] is already installed" instead %P format. Installshield might not know %P format & all. ... View more

Hi agshah, By default windows installer/msi's uninstall behavior would be : Asking for a confirmation about uninstallation Then it proceeds with removal of components It won't bring you up wizard with finish button If you want to accomplish that Installscript/Installscript MSI will be the option for you. Hope that helps, Thanks, Jenifer ... View more

Hi Jenifer, thanks for your response and the links. For the InstallScript project types, the links mention "You want to perform actions before or after the main installation is run" Does this mean this is not possible in 'Basic MSI' ? Currently we have an 'InstallScript MSI' project and there are issues with it and hence are looking into switching over to Basic MSI project type to see if it resolves the issues. In our existing 'InstallScript MSI' project type, we currently run an exe from installscript before the install dialog comes up and look up and store info that is used later in the InstallScript after the files have been copied over, etc. Will we not able to do these type of things in 'Basic MSI' ? ... View more

Hi agshah, Have you tried setting Release1->Signing->Sign Output Files-> to Setup.exe ? In which setup.exe inside cache folder ("C\Program Files (x86)\InstallShield Installation Information\{product guid}\setup.exe) will get signed.By which your problem of uninstalling from Apps & features will get solved Thanks, Jenifer ... View more

This issue seems to be because my project is InstallShield InstallScript MSI. I create Basic MSI and InstrallScript projects and they don't have this issue. Can someone please comment if this is a known InstallShield issue with the InstallScript MSI projects? If so, any workarounds ? ... View more

You'll need to parse the Date and Time strings returned into their constituent parts (year, month, day, hour, minute) and then concatenate them back into the desired order. ... View more

agshah, I don't know about the Date property, but this can be used in InstallScript: GetSystemInfo( DATE, nResult, strDate ); GetSystemInfo( TIME, nResult, strTime ); svDateTime = strDate + " " + strTime; reference: http://helpnet.installshield.com/installshield22helplib/Subsystems/installshield22langref/helplibrary/LangrefGetSystemInfo.htm HTH ... View more

What I meant was that the property you are looking for is "Installed". In your original post you used an undefined property "INSTALLED". There is a difference--property names are case sensitive. The reason I surmised that you wanted your action to be in the "Install UI Sequence" is that you said you wanted the action to display a message. You don't want to display messages in the "Install UI Execute" sequence because if you put the message there it will display if the user performs a silent (or unattended) installation. I'd recommend you look into taking Flexera's "Learning MSI Projects Using InstallShield" class. ... View more

Folks, anyone know how to customize this message? InstallShield displaying instead of product name is cryptic. Also, Add/Remove programs is not longer called Add/Remove programs since a long time. If it is not possible to customize this message, what are some other options to tell the user to uninstall an existing version before installing the current one? ... View more

InstallScript MSI projects create their own ARP uninstall key which is what is used as the source of the ARP entry (the MSI uninstall key is hidden from ARP). InstallScript MSI uninstall keys are under HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall and are always named 'InstallShield_{ProductCode}'. The uninstall string will always reference the cached setup.exe installed at \InstallShield Installation Information\{ProductCode} to allow the product to uninstall correctly. msiexec.exe can't be used to uninstall an InstallScript MSI project. If this is required a Basic MSI project should be used instead. ... View more