@lists.sourceforge.net; Bob Arnson
Subject: RE: [WiX-users] Handling Feature Dependencies
What version of WiX are you using? I found a bug with FeatureGroups
earlier in WiX 3
(https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1760155&gr
oup_id=105970
<https://sourceforge.ne
hich apparently has been fixed.
John
_
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 06 December 2007 06:21
To: [EMAIL PROTECTED]
Cc: John Hall; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Handling Feature Dependencies
[EMAIL PROTECTED] wrote:
light.exe : error LGHT0204 : ICE03: Not a valid foreign key; Table:
FeatureCompo
nents, Column: Feature_, Key(s):
grpRequiredModules.uplevel.66332652_9C28_58B1_F
F1F_C8B3B9A1E18E
That looks like it's a combination of the feature group name and
components from t
something similar to a "SuppressModularization" or am I missing
something else?
From: John Hall [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 04, 2007 10:02 AM
To: Robert Priest; [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Handling Feature Dependenci
Oh. Are you saying put the MergeRefs directly under the feature
groups? Okay. I will give that a shot.
Yes, and then put FeatureGroupRefs under your Features.
John
-
SF.Net email is sponsored by: Th
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
uding MergeRefs.
I did include it as you stated.
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 t
: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
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:
Featu
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 P
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.
FeatureGroupRefs can contain MergeRefs though.
John
--
[EMAIL PROTECTED] wrote:
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? W
en
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
@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
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 insta
Subject: [WiX-users] Handling Feature Dependencies
Hello,
Let's say I have three features - fA, fB, fC. All of these
features are at the same level - Level 1. But only fA and fB are shown
to the user. fB is hidden from the user and should be install
Hello,
Let's say I have three features - fA, fB, fC. All of these features are
at the same level - Level 1. But only fA and fB are shown to the user.
fB is hidden from the user and should be installed if fA or fB is
installed. If neither of those gets installed, fC should not be
installed.
18 matches
Mail list logo
