Trying to be tidy, I pulled out the CustomAction declarations relating
to a particular aspect of my install into its own .wxs file.
I have
<Fragment>
<CustomAction...>
<CustomAction...>
<CustomAction...>
<InstallSequence>
[...sequence the custom actions declared above]
</InstallSequence>
<Fragment>
Problem is, the InstallSequence seems to be ignored. I'm guessing that
this is because it's not referenced in the Product element, which lives
in a different file. How can cause InstallSequences defined in
fragments to be merged into the one in the Product? Is the only way to
use a .wxi include instead of a Fragment? Why then is Fragment a valid
parent for InstallSequence?
Thanks,
Jeremy
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
