Hi,

Can someone please explain me the 'processing' of custom action: ""Asynch, Wait at end of sequence ""

Asynch, Wait at end of sequence :
As per the help if processed in this way then windows Installer waits for the exit code from the custom action before continuing.

What does it do if exit code is success and what does it to do when exit code is failure.

Then what is the exact difference in ""Asynch, Wait at end of sequence "" and Synchronous, Ignore exit code.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
You can refer to one of the old thread of this forum by bheers : http://itninja.com/question/question
This has almost all details of Custom Action.
Answered 10/26/2010 by: murali.bhat
Purple Belt

Please log in to comment
0
Thanks murali..but it didn't help...this is copied directly from help file of Wise...

I am looking for precise answer.....

Anyone else please
Answered 10/26/2010 by: kermit99
Yellow Belt

Please log in to comment
0
I think the help file is pretty succint but if you're struggling...

The two essentials difference are that with 'Synchronous, Ignore exit code', the engine waits for the CA to complete before moving on to the next action and that CA's exit code is ignored. With 'Asynch, Wait at end of sequence' the engine runs the CA alongside the main thread and that the CA's exit code *is* checked but at the end of the sequence.

Does that help?
Answered 10/27/2010 by: VBScab
Red Belt

Please log in to comment
0
Ok.

I understand that exit code is checked in case of 'Asynch, Wait at end of sequence'

but what happens if exit code is success...

and what happes if exit code is failure...

I feel in both case installer continues.... so what is the use of checking the exit code...

I may be little confused with this...I think you may help??
Answered 10/27/2010 by: kermit99
Yellow Belt

Please log in to comment
0
Yes, the installation continues because you will have told the engine to 'wait at end of sequence' before processing any error codes.

If you want an error to be checked immediately after the CA's execution and exit on an error condition, use 'Synchronous'.
Answered 10/27/2010 by: VBScab
Red Belt

Please log in to comment
0
Still little confused....then what is the specific use of this processing....when things are same as synchronus, ignore exit code...
Answered 10/27/2010 by: kermit99
Yellow Belt

Please log in to comment
0
Synchronous means... supoose there are A1 , A2 ,Ca1,A3 are orgainsed in this sequence.Where A1,A2,A3 are the standard Action and Ca1 is Custom Action...here when we run appliaction A1 , A2 will run and it holds the Installation for MSI as it in synchronous ....and execute Ca1 ....now if the Ca1 fails then also the application will continue to install the further actions for MSI and execute A3....hence our application will be installed by ignoring the Ca1..

In case of asynchronous mode for the same example ...A1,A2 will execute and MSI installation for standard Actions is not kept on hold...where as one more thread for Ca1 is created in order to execute it....
Answered 10/27/2010 by: SM
Senior Yellow Belt

Please log in to comment
0
How are they the same? One ignores the error code, the other acts upon it, just not immediately.
Answered 10/27/2010 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity