User Interface VS Execute sequence Properties
Posted 08 September 2005 - 21:16
I have run into an issue: I set a MSI Property in custom action that is called in the execute sequence, and I want, at the SetupCompleteSucess, to launch 2 applications installed with the setup depending on the MSI Property that I have just set (in the execute sequence).
It seems that the value set in the execute sequence for my MSI property is not taken into consideration at SetupCompleteSucces.
I have tried to set it in another custom action called during User Interface sequence (let's say at click on a button on a dialog) and the value set for the property in this mode gets into the SetupCompleteSucces correctly.
What is the differrence between setting a property in UserInterface sequence or in the Execute section ? How can I "read" the value of a "execute seqence property" in the User Interface seqeunce?
I'm using Install Shiled 11 and a Basic MSI Project.
Thanks for all the help
Posted 14 September 2005 - 10:14
Posted 19 September 2005 - 07:04
Thanks for the answer but, I still have a problem.
As I tried to present my problem, to be able read from the registry, I need a code written in the script file right? So, to call that code I must call it in the UI Sequence, in my case, I cannot call that function (through CustomAction) in one previous Dialog, instead “Finish Dialog”, because it will be too soon for me. My custom action is called, let’s suppose, before “Install Finalize” and if I call the function in one window before some custom actions, which set up some properties, I cannot have those properties available yet.
You say that, on the “Finish Dialog” to call a custom action which read the value which has been set up in the execute sequence, BUT, as far as I know, at that moment, nothing from setup.rul script cannot be executed – I know that only the properties are taken in consideration in that moment but a InstallScript Custom Action cannot be executed.
Thank you very much for the support and I’m looking forward for another solution or idea
Posted 19 September 2005 - 12:32
Posted 20 September 2005 - 10:32
The only solution that I can see it is to write in to a file (suppose a *.ini file), or write in registry, and then, at the end of the installation, on Finish Dialog, call and EXE custom action, with the product installed, or something ... it doesn't like a good solution anyway.
One more question, where can i found or, it would be much better if you already know, what kind of custom actions are taking in consideration after the engine is stoped, becasue we already know that Installscript custom actions are not taken in consideration. i have tried some documentaiton, but without success.
Posted 20 September 2005 - 13:31