Oh. Are you saying put the MergeRefs directly under the feature groups?
Okay. I will give that a shot.

 

From: John Hall [mailto:[EMAIL PROTECTED] 
Sent: Monday, December 03, 2007 2:59 PM
To: Robert Priest; [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Handling Feature Dependencies

 

Robert,

 

What you need to do is put the MergeRefs under the FeatureGroup, and
then include the FeatureGroup using FeatureGroupRefs in the Features
that need the merge modules.

 

Cheers,

John

         

        
________________________________


        From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
        Sent: 03 December 2007 17:04
        To: [EMAIL PROTECTED]; John Hall
        Cc: wix-users@lists.sourceforge.net
        Subject: RE: [WiX-users] Handling Feature Dependencies

        Yes. That is true. But what I used is a FeatureGroup element.
Then, under the FeatureGroup Element, I use a mergeref.  So I have
something like:

         

          <Fragment>

                <FeatureGroup Id="grpRequiredFeatures">

                    <Feature Id="fC" Title="FeatureFC" Level="1"
Absent="disallow" Display="hidden">

                        <MergeRef Id="MFC" />

                        <MergeRef Id="MFCPolicy" />

                    </Feature>

                </FeatureGroup>

            </Fragment>

         

         

        But that still presents a problem because it appears you can't
include one feature under multiple features... Is that correct? I keep
getting:

         

        "error LGHT0095 : Multiple primary references were found for
Feature 'fC' ...

         

        Is there really no way to group these merge modules (and
possibly other components) together and use them under different
features. 

         

        Sounds like what I have to do is to include each MergeRef
multiple times.  So fA and fB must both include MergeRef MFC and
MergeRef MFCPolicy...  

         

        So if I have 10 merge modules that should get delivered with two
different features, I will end up with 20 MergeRef lines? Is there no
better way to group merge modules together and use them in different
features?

         

         

        BTW - part of me doing this is so that the "next" button on the
"Feature Selection" screen gets disabled. However, even when I have
nothing selected in the Feature Tree, the next button is still enabled.
How do I stop that?

         

         

        From: Bob Arnson [mailto:[EMAIL PROTECTED] 
        Sent: Monday, December 03, 2007 10:59 AM
        To: John Hall
        Cc: Robert Priest; wix-users@lists.sourceforge.net
        Subject: Re: [WiX-users] Handling Feature Dependencies

         

        John Hall wrote: 

        FeatureGroupRefs can contain MergeRefs though.

        
        Good point. I haven't needed FeatureGroups before.
        
        

        -- 
        sig://boB
        http://joyofsetup.com/

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to