3

I've created an MSI installer using Installshield 2014. While running it from UI everything works fine but when I run it in silent mode using below command then my custom actions are not firing at all:

C:\>msiexec /i "myApplication.msi" /qn WEBURL=http://localhost/mywebapp /log  out.txt

WEBURL is the property required by the custom action. Value of WEBURL is passed to C# class library method as an argument. The C# method is called by my custom action which gets called when I click on Install button on begin installation wizard step. My custom action gets executed always i.e. I've kept the condition for the execution of the custom action as 1 which means it executes under all circumstances.

In the log file I also see the value of WEBURL property getting correctly set. I'm not able to get as to what is stopping my custom action to fire while running the installer in silent mode?

Update: As suggested by Michael, after putting the custom action in InstallExecuteSequence it starts getting executed in silent mode. But now the problem is that it starts getting executed twice in UI mode as the same action was already getting executed through a button click on one of the dialogs which appears during InstallUISequence. So I want to execute my custom action by putting it into InstallExecuteSequence only when I'm running the installer in silent mode (so that it executes only once if I'm in UI mode).

RBT
  • 24,161
  • 21
  • 159
  • 240

1 Answers1

1

When you run with /qn, the wizard is not shown. Even the entire InstallUISequence is skipped. So if you want your action to always run, you should not invoke it only from a button click. When the button isn't shown, it cannot be clicked.

Instead find a spot in the InstallExecuteSequence to schedule it. (If you have no other requirements, you probably still want to schedule it sometime after CostFinalize to mirror the non-silent case.) This scheduling will run the action whether or not you have UI.

However, it also runs it whether you are installing or uninstalling, so either alter your condition or your action to take that into account. The simplest approach may check whether the Installed property is set; a more robust check may verify the install and action states of a relevant component. The latter can be necessary if you need to conditionally do something in maintenance scenarios that add or remove a feature.

Since you mention you also need it to run during the UI, you have to take extra steps. You may be able to set the msidbCustomActionTypeFirstSequence scheduling option as shown below.

enter image description here

Or you may have to detect the scenario, for example by checking UILevel, or by setting and checking your own property when your action runs. You may also need to split it into multiple entry points so you can tell UI from immediate Execute; there does not appear to be a RunMode that distinguishes the two. (Am I forgetting a property that gets set?)

RBT
  • 24,161
  • 21
  • 159
  • 240
Michael Urman
  • 15,737
  • 2
  • 28
  • 44
  • If I put my custom action in `InstallExecute` sequence then it will run both in UI and silent mode. In UI mode it runs twice, one from one of the UI dialogs and other from the `InstallExecute` sequence. I can't remove it from UI dialog as I might have to run it there multiple times based on some UI checks. How can I ensure that even if I add a custom action in `InstallExecute` sequence then it fires *only* in silent mode. – RBT Jan 24 '17 at 08:14
  • @RBT: I updated my answer to talk about FirstSequence and UILevel as options to execute only in one sequence. – Michael Urman Jan 24 '17 at 13:02
  • Custom Action Scheduling option did the trick for me. All my custom actions were scheduled as `Always execute`. The moment I changed it to `Execute only once` it started working as per my expectation. I believe `UILevel` thingy can also be relevant in my scenario but we support *only* two modes in our installer `INSTALLUILEVEL_FULL` and `INSTALLUILEVEL_NONE`. I would have used it if I needed that level of control while executing my custom actions. I've also added a screen-shot to showcase my execution scheduling changes in your post as it will help the readers. Thank you for the follow-ups. – RBT Jan 25 '17 at 07:02