This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- How to suppress AskYesNo dlg
Subscribe
- 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
‎Aug 03, 2011
06:52 AM
How to suppress AskYesNo dlg
I have one MSI project in which i wrote an install script custom action and sequenced it to execute during Uninstallation. Inside the customaction there is an AskYesNo() function. Normal uninstallation the message is popping up and thats the desired behavior too.
My problem here is that when i try the silent uninstallation with /q or /qn or /qb still only that dialog is popping up.
Is there any way to suppress this AskYesNo dialog?
Can anyone provide some information on this?
My problem here is that when i try the silent uninstallation with /q or /qn or /qb still only that dialog is popping up.
Is there any way to suppress this AskYesNo dialog?
Can anyone provide some information on this?
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 03, 2011
10:38 PM
You can either check from inside of your InstallScript custom action if it is running silently, or set a condition on the said custom action so that it will not run in silent mode.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 03, 2011
11:42 PM
Thanks for that hint. The issue i had spotted when i am doing the major Upgrade and since the earlier product that is already installed in the machine is having this issue is there anything that i can do to supress it from my new installer?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 04, 2011
02:12 PM
Other than modifying the cached MSI, the answer is no. That's one reason why there shouldn't be any prompt for user input during Execute Sequence.