Hey Jeremy, In order to include code inside a fragment you must reference something. >From the below snippet you provided you could reference a single CustomAction using <CustomActionRef<http://wix.sourceforge.net/manual-wix3/wix_xsd_customactionref.htm>/>. This will link in the rest of the fragment.
Thanks, Brian Rogers "Intelligence removes complexity." - Me http://icumove.spaces.live.com On Wed, Jan 21, 2009 at 8:32 AM, Jeremy Lew <j...@liquidmachines.com> wrote: > 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
