Hello everyone, In my installer I set multiple registry values through InstallScript, however right now I do this in a less than ideal way: Here an example on how I set the InstallDir property: 1. I create a CustomAction 'MakePropertiesAvailableForSetRegKeyValueForInstallDir'      a. I set the Property Name: SetRegKeyValueForInstallDir and the Property Value: [INSTALLDIR] 2. I create a CustomAction 'SetRegKeyValueForInstallDir'      a. I set the Function Name CreateInstallDirRegistryKeyAndSetValue 3. I add the following code to the InstallScript Setup.rul file:     export prototype CreateInstallDirRegistryKeyAndSetValue(HWND); function CreateInstallDirRegistryKeyAndSetValue(hMSI) STRING szKey, szNumName, szNumValue, svNumValue, szTitle, szMsg; NUMBER nType, nSize, nvType, nvSize; begin szKey = "Gomocha"; // Create "Gomocha" registry key in HKEY_CLASSES_ROOT if (RegDBCreateKeyEx (szKey, "") < 0) then MessageBox ("Creating the registry key failed.", SEVERE); abort; endif; nvSize = MAX_PATH; MsiGetProperty(hMSI, "CustomActionData", szNumValue, nvSize); szNumName = "InstallDir"; nType = REGDB_STRING; nSize = -1; RegDBSetKeyValueEx (szKey, szNumName, nType, szNumValue, nSize); end;       This works fine, but I have 26 properties that I want to add in the registry. Is there a more easy way to set these through InstallScript? Can anyone show me a clear example?   Ideally I want to setup multiple properties so: [INSTALLDIR],[BACKUPDIR],[SORTIMPORT] And then loop over them, I just have no clue how to do this in InstallScript.  I'm using InstallShield 2023 R1. ... View more

Hello everyone, We create multiple builds per day and I want to create an installer for each build, each build should also be able to be upgraded from, that's why I want to use a major upgrade. Our product consists out of multiple IIS websites and a BizTalk installation, so I cannot use regular patches. If I understand correctly, InstallShield doesn't overwrite any assemblies if there is a small codechange without the assembly number being increased. I was wondering if it is possible to create a major upgrade for each build I'm doing using Azure DevOps. Changing the Upgrade Code should be enough right? Can I pass in some sort of commandline argument into the InstallShield build task to do this?     ... View more

All, The flow of my current Basic MSI setup is as follows: 1. Create a custom action 'MakePropertiesAvailableForRegistryInsertX' 2. Create a custom action 'CallInstallScriptThatInsertsProperty' 3. The InstallScript has the following:         export prototype CreateProcessInParallelRegistryKeyAndSetValue(HWND); function CreateProcessInParallelRegistryKeyAndSetValue(hMSI) STRING szKey, szNumName, szNumValue, svNumValue, szTitle, szMsg; NUMBER nType, nSize, nvType, nvSize; begin szKey = "Gomocha"; // Create "Gomocha" registry key in HKEY_CLASSES_ROOT if (RegDBCreateKeyEx (szKey, "") < 0) then MessageBox ("Creating the registry key failed.", SEVERE); abort; endif; nvSize = MAX_PATH; MsiGetProperty(hMSI, "CustomActionData", szNumValue, nvSize); szNumName = "ProcessInParallel"; nType = REGDB_STRING; nSize = -1; RegDBSetKeyValueEx (szKey, szNumName, nType, szNumValue, nSize); end;     For each property that I want in the registry, I follow the above 3 steps, which can get ugly when I have 20+ properties that I would like to set.  What I would like is the following: Insert a property into registry at Gomocha\ComponentName\Property1 Insert a property into registry at Gomocha\ComponentName\Property2 I tried adding multiple properties into the installscript by passing in the following into the 'MakePropertiesAvailable' custom action: [PROPERTY1];[PROPERTY2];[PROPERTY3]; But that resulted in szNumValue to be showing up empty in the messagebox:   export prototype CreateGatewayFileAdapterRegistryKeyAndSetValue(HWND); function CreateGatewayFileAdapterRegistryKeyAndSetValue(hMSI) STRING szKey, szNumName, szNumValue, svNumValue, szTitle, szMsg; NUMBER nType, nSize, nvType, nvSize; begin szKey = "Gomocha"; // Create "Gomocha" registry key in HKEY_CLASSES_ROOT if (RegDBCreateKeyEx (szKey, "") < 0) then MessageBox ("Creating the registry key failed.", SEVERE); abort; endif; nvSize = MAX_PATH; MsiGetProperty(hMSI, "CustomActionData", szNumValue, nvSize); MessageBox ("CustomActionData" + szNumValue, SEVERE); szNumName = "XSLTPath"; nType = REGDB_STRING; nSize = -1; RegDBSetKeyValueEx (szKey, szNumName, nType, szNumValue, nSize); szNumName = "ExportedPath"; RegDBSetKeyValueEx (szKey, szNumName, nType, szNumValue[1], nSize); szNumName = "SortImportFilesByFileName"; RegDBSetKeyValueEx (szKey, szNumName, nType, szNumValue[2], nSize); szNumName = "ProcessInParallel"; RegDBSetKeyValueEx (szKey, szNumName, nType, szNumValue[3], nSize); end;         I probably have to split the szNumValue into a list using StrGetTokens? Could someone provide an example?    Is there a better way to "debug" installscript? Instead of adding the MessageBox(szNumValue, SEVERE)? ... View more

Hi everyone, I have a question regarding prerequisites/redistributables. Right now every time when I run my installer I get the prerequisites screen: But these prerequisites are already installed. I was expecting InstallShield to detect this automatically. Is this a setting on the prerequisite itself?  ... View more

  Hi everyone,  I set up a CustomAction to execute a batch file which does a bunch of sqlcmds. When the batch file comes up the user has to enter some data, but instead of the proper text it is showing: The system cannot find message text for message number 0x2371 in the message file for Application.   Does anyone know why this is happening? Before this was working fine, as far as I know I didn't change anything. If I run the batch file manually it is working fine.    ... View more

Hi All, I currently have the installation process done, so now I'm working on getting the update process to work, but I'm not entirely sure how this works in InstallShield. From what I understood is that InstallShield only replaces files if the version number is greater than the previous version, unless you use Patch Optimization. First question: how do I run Patch Optimization if I have a compressed setup.exe? I can't select my setup.exe as a 'previous patch'. Do I have to build both compressed (for public release) and uncompressed (for internal use)? Is that how other companies do it?   I use dynamic file linking for all components, can I somehow make sure that everything is being overwritten when upgrading? How do I do this? Thanks in advance. ... View more