3 replies to this topic

[vishalv]

Hi guys,

I have a strange problem when upgrading from version 1 to version 2 to version 3 on a major upgrade.

Whenever a major upgradeis done I take a backup of the data and create a registry key which is required to set a condition in the custom action.
This goes fine and I am able to perform an upgrade. But when I try to upgrade the upgraded version to version3 the same backed up data folder and the registry entry are deleted.

Is this some known issue or am I missing something? I was able to solve the deletion of data by appending the current version number to backed up data folder so that every time an upgrade is performed a data will be backed up in a new folder. Is installshield intelligent enough to delete the reg entry and the folder during an upgrade from version2(upgraded from version1) to version3?

Also is there any way I can prevent the custom actions being run on a windows Auto Repair.

Regards,
vishalv

[Stefan Krueger]

A major upgrade is basically an uninstall of the old version. So if the folder is set to be removed during uninstall, this will also happen during a major upgrade. How do you create that backup folder and registry entry?

[vishalv]

Hi Stefan,
I take a backup of the registry and create the registry during the OnBegin function just before the Welcome dialog comes up.

Also sometimes a component fails to get installed and kicks of the auto repair option rerunnning the entire installation including the Custom Actions. Is there a way to prevent an auto repair or prevent custom actions being launced during a autorepair?

Thanks,
Vishal

[Stefan Krueger]

Oh, the mixture of InstallScripting and MSI can be a problem. Maybe a combination of Disable/Enable(LOGGING) and use of the system variable MAINTENANCE can get the job done.