3 replies to this topic

[Gig52]

I need to have a Custom Action that will act like the project condition. I already have the usual project condition where you need to have administrator rights to perform the installation.

Now, what I need is based on the AppSearch results to validate the property returned and perform some action: Confirm action with user, uninstall legacy or Abort install.

So, where should the CA be sequenced? After AppSearch..
What type should it be?? Immediate or deferred??

Note that I would like this to happen before the first dialog for user input is shown (usually this is the Welcome dialog).

Thanks

[Stefan Krueger]

If you want to have it before the dialogs, you must put it in the User Interface sequence, and therefore it has to be Immediate. Deferred actions are only possible in Execute sequence between InstallInitialize and InstallFinalize.
In addition you may need to put a similar action into the execute sequence (but without aksing any questions) in case your setup runs in silent mode (the UI sequence is ignored in this case)

[Gig52]

The CA gets called but with errors...

I tried with a InstallScript MSI project from scratch and only added a CA with Installscript code that display a message box and I have the following errors:

Return processing is Synchronous (Check exit code)
Action start 22:53:07: test.
1: RPC runtime reported exception 0x6ba
Action ended 22:53:07: test. Return value 3.
1: Failed to launch action 'test', error is 1603

Return processing is Synchronous (Ignores exit code)
Action start 22:50:39: test.
1: RPC runtime reported exception 0x6ba
Action ended 22:50:39: test. Return value 1.

Why is the exception 0x6ba always present?? (both cases).
What is the definition for 0x6ba?? (RPC server error !!!)

[Stefan Krueger]

If you're using InstallScript MSI I'd recommend calling it from your script.
However Basic MSI is preferrable in most cases.