Yes, exactly.You place actions relative to the actions they need to be
associated with. They'll be placed as close as possible.
2011/9/17 Frédéric Viollet
> Hi Rob,
>
> I agree that starting services would be difficult before installing files
> ;)
> But in a pure logical way,
>
>
>
> does not m
Hi Rob,
I agree that starting services would be difficult before installing files ;)
But in a pure logical way,
does not mean that CustomAction2 will be executed after InstallFiles. It
just means that it will be executed before StartServices...
Why wouldn't the sequence be :
CustomAction2 -> I
Because StartServices can't start services before the files for the services
are installed.
2011/9/16 Frédéric Viollet
> Hi Rob,
>
> Do you mean that if I write:
>
>
>
>
> Or
>
>
>
>
> In both cases, I'm sure that CustomAction1 will be executed after
> InstallFiles, that CustomAction2 will
Hi Rob,
Do you mean that if I write:
Or
In both cases, I'm sure that CustomAction1 will be executed after
InstallFiles, that CustomAction2 will be executed after CustomAction1
and before StartServices?
If so, what's the logic associated to these After and Before attributes?
Why would
Pick one.
2011/9/15 Frédéric Viollet
> Hi All,
>
> I have defined two custom actions and I would like it to be triggered
> after InstallFiles, but before StartServices.
> Lets say I want to setup the following sequence:
> InstallFiles -> CustomAction1 -> CustomAction2 -> StartServices
>
> I woul
Hi All,
I have defined two custom actions and I would like it to be triggered
after InstallFiles, but before StartServices.
Lets say I want to setup the following sequence:
InstallFiles -> CustomAction1 -> CustomAction2 -> StartServices
I would have liked to write:
But, in the wxs, Before and
6 matches
Mail list logo