InstallShield Professional Edition - Custom Action - Setup.exe vs MSI

0
votes

I have a windows forms application (Add-In Express Solution) for which I have created an InstallShield setup project which uses custom actions (Auto generated by Add-In Express). The custom actions are launching executable files (The executable files are used to register the Add In).

When I generate a setup.exe file for the project, everything works well. The custom actions are running and the add-in is being correctly installed.

When I generate an msi file (Uncheck "Create installation launcher" option in the Release Wizard of Installshield) then the custom actions aren't running (add-in not installed but the program shows up in the list of programs in the Control Panel) when I try installing the product.

Am I required to use the setup.exe version when using custom actions or am I not configuring my project correctly when trying to generate an msi file?

2
windows-installerinstallshieldsetup.exe
Run the MSI with "/L C:\LOG.txt". In the Logfile you find your CustomAction "Skipping Action:..." and why the Action is not executed. (e.g. the Setup.exe passes a Parameter to the msi: /v"RUNCA=true". Without Setup.exe "RUNCA" is false ) – Marc
Thank you for the help Marc. The logs are showing that the custom actions are being run. I noticed that when I run the MSI via a command prompt in Administrator mode it works fine. If I run the MSI via a command prompt without admin privileges it will ask me for the privileges but won't install the add in and the logs show no errors. I think I should be able to work with that. – DDA

2 Answers

3
votes

The difference between running the MSI directly or using a Setup.exe is the point in the sequence the user rights get elevated.

if you run the Exe, you will probably recieve a UAC Popup requesting more rights, you click OK and everything will run elevated(with admin rights).

if you run it from an already elevated command prompt also everything will run elevated.

if you run the msi normally(e.g. doubleclick it) it will run through the whole installUIsequence then it will run through the installexecute sequence and when it reaches the InstallInitialize Action it will request elevated rights.

and as soon as the InstallFinalize action is run the rights are dropped.

so you need to place the custom actions which need admin rights after the InstallInitialize and before InstallFinalize action

0
votes

What I ended up doing to solve my issue is set the custom actions to run in the System Context.

In-Script Execution: Deferred Execution in System Context