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
- :
- Insisting cutomer to use setup.exe instead of setup.msi
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
Mar 02, 2009
02:14 PM
Insisting cutomer to use setup.exe instead of setup.msi
I have a basic MSI project application and generating setup.exe & setup.msi.
Application is already installed on the machine. When customer click on setup.msi or setup.exe ( from the Installation folder), it goes to maintenance mode ( this is the right behaviour).
What i need is, when customer click on setup.msi...instead of going into maintenance mode, i would like to display a message box saying , please use setup.exe and not to launch maintenance mode.
Thanks for your help.
Application is already installed on the machine. When customer click on setup.msi or setup.exe ( from the Installation folder), it goes to maintenance mode ( this is the right behaviour).
What i need is, when customer click on setup.msi...instead of going into maintenance mode, i would like to display a message box saying , please use setup.exe and not to launch maintenance mode.
Thanks for your help.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 02, 2009
10:30 PM
You can encourage and nudge, but not really insist.
You could have the setup launcher set a public property on the msiexec command line and your msi could have a launch condition that tests for the property having that value. You can't, however, prevent users from cracking open the msi and either specifying the same property themselves on a command line or removing the launch condition from the msi (remember that the msi file isn't a black box but one that can be examined by users with the proper tools (InstallShield, ORCA, etc.).
You could have the setup launcher set a public property on the msiexec command line and your msi could have a launch condition that tests for the property having that value. You can't, however, prevent users from cracking open the msi and either specifying the same property themselves on a command line or removing the launch condition from the msi (remember that the msi file isn't a black box but one that can be examined by users with the proper tools (InstallShield, ORCA, etc.).
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)