- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Permanent Prerequisite
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
I have a basic MSI that also installs/checks SQL Server native client (specific build) as a prerequisite. The problem I am running into is that it seems to be uninstalling it when I uninstall my MSI. I don't want it to do that. Is there a way to mark it as "permanent" or disable the action that uninstalls prerequisites (which action is it)?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
User error...
The problem had nothing to do with prerequisites. Just a bloody coincidence that the files being removed from SYSTEM32 folder were also the files that were being installed by the prerequisite. I moved one of my custom actions before CostFinalize (intentionally) and some of the properties were not initialized at that stage, so my script defaulted to run under SYSTEM32 directory and wreaked havoc...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @nikita_osipenk ,
What is the option you had chosen when you selected pre-requisite ,New Feature or Install before feature selection?
With both the options i couldn't see that uninstall behavior with InstallShield built in pre-requisite msi.Unless untill we mention specifically uninstall might not get triggered i guess.
Is there anything specific to the pre-requisite msi you had added?
Thanks,
Jenifer
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
User error...
The problem had nothing to do with prerequisites. Just a bloody coincidence that the files being removed from SYSTEM32 folder were also the files that were being installed by the prerequisite. I moved one of my custom actions before CostFinalize (intentionally) and some of the properties were not initialized at that stage, so my script defaulted to run under SYSTEM32 directory and wreaked havoc...