About Xylene

Xylene · ‎Aug 31, 2016

Xylene wrote: Is there a way for a currently installed application to know that the the request to uinstall came from an UPGRADE and not from a user selecting to uninstall the application? I found the answer to my question from The windows developer resources https://msdn.microsoft.com/en-us/library/windows/desktop/aa372380(v=vs.85).aspx "The UPGRADINGPRODUCTCODE property is set by Windows Installer when an upgrade removes an application. The installer sets this property when it runs the RemoveExistingProducts action. This property is not set by removing an application using the Add or Remove Programs in Control Panel. An application determines whether it is being removed by an upgrade or the Add or Remove Programs by checking UPGRADINGPRODUCTCODE."

Xylene · ‎Aug 29, 2016

Is there a way for a currently installed application to know that the the request to uinstall came from an UPGRADE and not from a user selecting to uninstall the application?

Xylene · ‎Aug 23, 2016

PlinyElder wrote: Are you also changing the Product Code for the application? No I didn't change the product code, is this needed just to check if the min version of the current product is already installed?

Xylene · ‎Aug 23, 2016

That is what I have setup now. I created a Major upgrade item with a min version, but it still runs through the installer and doesn’t exit. Is there something more I need to do? Do I need to check the Detect Property and then have that trigger the exit?

Xylene · ‎Aug 23, 2016

How do I make an install that is requires a certain version of the same product to be installed before allowing the newer version to be installed. I want to make sure that the current product version is at least X before allowing the upgrade. When I attempt to use the Automatic upgrade item with a min version number it still just runs the upgrade regardless if that version number is installed or not.

Xylene · ‎Aug 22, 2016

PlinyElder wrote: It kind of depends on where that needs to be set. In suite projects you can set IsInstallMode=remove and in MSI projects you set REMOVE="ALL" for CustomAction sequence conditions. There is also some msi properties you can set to adjust the REINSTALLMODE, see Windows Install property reference In this particular case I want to update the old installer (or remove) but I don't want to prompt to unconfigure the product.

Xylene · ‎Aug 22, 2016

As an update, the old installer does check the REMOVE=ALL property and that triggers the uninstall which calls (all of the time) the unconfigure function. So as part of the uninstall the prompt to unconfigure is always called.

Xylene · ‎Aug 22, 2016

PlinyElder wrote: Do you have access to the code from the old installer? More than likely that prompt is triggered by some type of property value. For example if the old installer sees that the setup.exe is running in a mode of REMOVE=ALL then trigger this custom prompt. You would have to know what the old installer uses to trigger the CA in order to possibly pass a value to that property to force it to bypass the CA prompt. Yes I have access to the old code. It seems like the CustomAction script is stored in the MSI database. Can the new installer set the REMOVE=ALL option prior to uninstalling the old installer? Where is the "REMOVE" variable stored?

Xylene · ‎Aug 18, 2016

I am new to Install Shield and am trying to solve a problem I have been tasked with. Basically our old install uses a customAction to call an user defined Install Shield function. That function then prompts the user if they want to unconfigure (Not remove) the product. If yes it launches an external binary with an unconfigure flag. Once unconfigured the installer then proceeds to remove the product. Fast forward to today. Now we have a new version of the product we want to roll out and I need to update the installer to handle what I am calling a migration. I essentially want the new installer to overwrite the old install files, or remove, and then lay down the new install files. What I am running into though is that I am not able to stop the old installer from first asking the end user if they want to unconfigure the product (The customAction is being triggered) Is there anyway to just overwrite the old install, update the product version and then carry on as if the product is now being installed, without having to run the old installers uninstall? Or if I do have to run the old installers uninstall can it be overwritten with a newer uninstaller so the CustomAction isn't called?

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:11 PM

Re: Upgrade vs. Uninstall

Upgrade vs. Uninstall

Re: Contingent Upgrades on previous product version

Re: Contingent Upgrades on previous product version

Contingent Upgrades on previous product version

Re: How do I overwrite an old installers customActions with something from my new install

Re: How do I overwrite an old installers customActions with something from my new install

Re: How do I overwrite an old installers customActions with something from my new install

How do I overwrite an old installers customActions with something from my new install

Re: Upgrade vs. Uninstall

Upgrade vs. Uninstall

Re: Contingent Upgrades on previous product version

Re: Contingent Upgrades on previous product version

Contingent Upgrades on previous product version

Re: How do I overwrite an old installers customActions with something from my new install

Re: How do I overwrite an old installers customActions with something from my new install

Re: How do I overwrite an old installers customActions with something from my new install

How do I overwrite an old installers customActions with something from my new install