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
- :
- Custom Actions During Maintenance issues
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
Oct 02, 2015
01:13 PM
Custom Actions During Maintenance issues
I have custom actions to run during maintenance, but need to know whether it is installing/repairing or uninstalling. Is there a way to do this?
I would prefer to run an executable, but those apparently can't access install properties. The conditions available to select for launching an executable don't give access to this either (only based on operating system, software, or feature -- only one feature 'Always Install'). Under software there is an option to create a new requirement, but these are only for file path, folder path, or registry entry.
I have heard that scripts can access install properties. Would using a VBS allow me to distinguish the current process? Is there something better than using VBS to access install properties and set an environment variable, then calling my executable, having it read the environment, do its action, then delete the variable?
Upgrading to Express might be an option, but it sounds like it wouldn't help. Upgrading to Professional or Premium is *not* an option.
I would prefer to run an executable, but those apparently can't access install properties. The conditions available to select for launching an executable don't give access to this either (only based on operating system, software, or feature -- only one feature 'Always Install'). Under software there is an option to create a new requirement, but these are only for file path, folder path, or registry entry.
I have heard that scripts can access install properties. Would using a VBS allow me to distinguish the current process? Is there something better than using VBS to access install properties and set an environment variable, then calling my executable, having it read the environment, do its action, then delete the variable?
Upgrading to Express might be an option, but it sounds like it wouldn't help. Upgrading to Professional or Premium is *not* an option.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 05, 2015
03:03 PM
For LE and Express, you will need to have the check for certain properties inside custom actions.
As you mentioned, the built in conditions does not fit what you require.
The article below should help with what you want to check.
http://resources.flexerasoftware.com/web/pdf/archive/IS-CHS-Common-MSI-Conditions.pdf
As you mentioned, the built in conditions does not fit what you require.
The article below should help with what you want to check.
http://resources.flexerasoftware.com/web/pdf/archive/IS-CHS-Common-MSI-Conditions.pdf
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)