Okay. So what if the hidden fC actually contains a merge module
(meaning, a< MergeRef /> element)? But I still don't want fC displayed
in the interface anywhere. AFAIK, ComponentGroupRefs do not contain
MergeRefs.
Should I make fC an sub-Feature of fA and fB? Will it still be hidden
from the interface if I do that?
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, October 16, 2007 11:23 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Handling Feature Dependencies
Thanks for the info guys.
I will try these solutions and let you know how it goes.
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 16, 2007 1:10 AM
To: John Hall
Cc: Robert Priest; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Handling Feature Dependencies
John Hall wrote:
However, in hindsight, I think just using a ComponentGroupRef instead of
feature fC and including it in both fA and fB might be simpler and more
robust. Not sure what the relative downsides are.
If the feature was used just for grouping (i.e., it's never visible or
user installable) then a component group is the best approach.
Components can belong to multiple features just fine -- that's an MSI
thing.
--
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
