I know it is possible to use MSI properties to update XML attributes, values, and content. I am wondering if it is possible to use MSI properties as part of the XPath to target specific XML elements. functionality described here: https://community.flexera.com/t5/InstallShield-Knowledge-Base/Target-XML-elements-with-specific-attributes/ta-p/4542   For example, if I want to use the XML File Change feature to find in a config file the path: /configuration/appSettings/add[@key="myKey" and @value="[MY_MSI_PROPERTY]"] ... View more

I'm running into a scenario with a chained MSI package that I'm unsure how to resolve: - Install Main product version 1 that has chained Sub Component version a - Install a standalone update to Sub Component to version c - Attempt a Major Upgrade for Main product to version 2 that has a chained Sub Component version b (older version than c)   The upgrade fails because it tries to run the sub component installation which says there is newer version installed. The main product treats this as a failure and stops the upgrade. Is there a way to prevent the sub component from running if there is a newer version already installed (ideally without having to manually check)? Or for the main product to consider the "new version failure" as not a failure so that it continues on? ... View more

Hello, First, let me give a little background to my situation. Currently, I have an installer (MSI) that installs a 32 bit driver when installed. Recently, we have created a 64 bit version of the driver and need to distribute that too. Obviously, the ideal situation is to update the already existing MSI installer to figure out which platform the user is installing on and deliver the appropriate driver. I know that simply adding it to the installer doesn't work due to Difxapp and so I've tried a couple different avenues. I tried creating a merge module for each driver and associating each to a different feature but installshield apparently didn't like that either. So now what I've done is create an installer for each driver package and make them feature prerequisites in the main MSI installer. This seemed to be going fine until I was testing the upgrade path from the previous installer. Basically, the installer is installing the feature prereq before removing the previous version (i.e. Major Upgrade) which actually completes the installation but the driver gets removed. My question is is it ok to put the ISInstallPrerequisites into the Execute action after the RemoveExistingProducts action? Or is there a better solution? I'm open to other solutions for the initial problem but everything that I have seen so far haven't seemed to be very elegant solutions. Thanks! ... View more

Hello, I am having an issue that I'm guessing I'm just missing something really simple. I have a basic MSI project and a current release out in the field. We are developing a Major Upgrade for our next release. The problem I am running into is that there are properties set during install of the previous release, that I want the Major Upgrade to pre-populate with. For example, if the user chose a different INSTALLDIR than the default, during the Major Upgrade install, the INSTALLDIR property should be set with the custom value. This seems like a common thing someone would want but I just can't find the mechanism to do it. Any help would be great. Thanks! ... View more

I am having an issue with our installer that I can't seem to figure out. After installation, if a user removed all permissions from a file that was installed (Don't ask me why they would just bare with me) and then they try and uninstall the software. I would expect they get and error stating the installer couldn't remove the file but what actually happens is the installer says it completed successfully and the file remains on the system. I checked the log created after uninstallation and there is an "Info 1321" line (not an Error 1321 which is what I would expect) stating there isn't enough privileges to modify the file. Is there a way I can elevate the warning to an error or anything like that? ... View more