I posted a bug on this, but I got it classified as invalid, since you can
use CustomActionRef; as Bob wrote.
What I did was to include an empty ComponentGroup in the fragment, and a
reference to the component group from Product.wxs, this way I don't need to
set a CustomActionRef for every custom action.
Kind of:
<Product>
<Feature>
<ComponentGroupRef Id='CAGroup' />
</Feature>
</Product>
<Fragment>
<ComponentGroup Id='CAGroup' />
<!--ALL Custom Actions go here -->
</Fragment>
-----Original Message-----
From: Bob Arnson [mailto:[email protected]]
Sent: Wednesday, January 21, 2009 6:42 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] InstallExecuteSequence in a fragment?
Jeremy Lew wrote:
> 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?
>
CustomActionRef
--
sig://boB
http://joyofsetup.com/
----------------------------------------------------------------------------
--
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
