[wix-users] Can anyone give me a nice simple example of returning values from a Custom Action?

[Paul Mumford]

Hi Jospeh, thanks for replying!

Yes the cases of the values are correct but to be certain ive just changed
them all to be upper case both in the c# code and the wxs. Like the man
says in alien, 'its the only way to be sure' :) Didnt make any difference.

With regards to costing:
a) I only vaguely know what that means, i think its the sequence of the UI
bit that determines the presents size of the install right? I dont know if
its related but we decided to use the '"WixUI_Minimal" instead of the Mondo
one (we just dont need the extra bits for this application). The custom UI
runs straight after the user ticks the accept license and presses install
which is fine and what we want.

I think you are onto something with the scheduling though, what would you
recommend for our requirements there? The various types are listed but I
dont really know what any of them mean. 'InstallValidate' makes sense in my
head but i suppose the point im after is directly after user presses
install button and before the actual MSI actions if that makes sense.

PS.
Could someone tell me the etiquette of replying to the mailing list, im
new. Should I reply to the group in general or just individuals or both?
Cheers P.


On 12 September 2017 at 16:22, Joseph L. Casale <jcasale at activenetwerx.com>
wrote:

> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf
> Of Paul Mumford via wix-users
> Sent: Tuesday, September 12, 2017 2:05 AM
> To: wix-users at lists.wixtoolset.org
> Cc: Paul Mumford <paul.mumford at gmail.com>
> Subject: [wix-users] Can anyone give me a nice simple example of returning
> values from a Custom Action?
>
> > In c# I say:
> >
> > session["THING_INSTALL_TYPE"] = "Client";
>
> >              * <Condition>**THING_INSTALL_TYPE = "Client"</Condition>*
> >             </Component>
>
> Are you certain you are writing the value in the case that your
> conditional checks with?
> It may be more robust to check for the value case insensitively.
>
> Also, I believe you are scheduling this too late, InstallValidate runs
> after costing
> and it's costing which indicates what is about to be installed so the
> condition is
> evaluated before.
>
> jlc
>