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=detailatid=642714aid=1760155gr oup_id=105970 https://sourceforge.net/tracker/?func=detailatid=642714aid=1760155gr oup_id=105970 ), which 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 the merge module. Sounds like a bug in the linker -- can you file a bug on SF? -- 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
Re: [WiX-users] Handling Feature Dependencies
That may be it. I am using 3.0.2925.0. I will upgrade to the latest weekly release (looks like right now its 3.0.3530.0) , and try that. I will let you know how it goes. From: John Hall [mailto:[EMAIL PROTECTED] Sent: Thursday, December 06, 2007 5:16 AM To: Robert Priest Cc: wix-users@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=detailatid=642714aid=1760155gr oup_id=105970 https://sourceforge.net/tracker/?func=detailatid=642714aid=1760155gr oup_id=105970 ), which 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 the merge module. Sounds like a bug in the linker -- can you file a bug on SF? -- 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
Re: [WiX-users] Handling Feature Dependencies
Light.exe does not like that. It throws: 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 light.exe : error LGHT0204 : ICE03: Not a valid foreign key; Table: FeatureCompo nents, Column: Feature_, Key(s): grpRequiredModules.downlevel_manifest.8.0.50727 .96.66332652_9C28_58B1_FF1F_C8B3B9A1E18E The name of my FeatureGroup is grpRequiredModules but it looks like candle.exe tacks on a few other items when compiling Do I need to do 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 Dependencies 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: 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
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 the merge module. Sounds like a bug in the linker -- can you file a bug on SF? -- 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
Re: [WiX-users] Handling Feature Dependencies
Thanks For the Response John, But that is what I did with the segment below. It kept giving me, this error however - error LGHT0095 : Multiple primary references were found for Feature 'fC' ... Or Am I missing something in my Fragment? It is a FeatureGroup including 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 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
Re: [WiX-users] Handling Feature Dependencies
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 - 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
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
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
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
Re: [WiX-users] Handling Feature Dependencies
[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? Will it still be hidden from the interface if I do that? Should work, using @InstallDefault=followParent and @Display=hidden. -- 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
Re: [WiX-users] Handling Feature Dependencies
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
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/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[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 installed if fA or fB is installed. If neither of those gets installed, fC should not be installed. Now what the seemingly obvious answer is, is to add a condition to fC on the order of: Feature Id=fA Level=1 /Feature Feature Id=fB Level=1 /Feature Feature Id=fC Level=0 Display=hidden Condition Level=1![CDATA[ (fA = 3) OR (fB = 3)]]/Condition /Feature But that does not seem to work. What am I missing? Is this not the proper way to evaluate a Feature condition that is based on the selection of other features. Can I not do the evaluation of the condition in fC in the FileCost action since the feature selection is there? Can I make fC a sub-feature of both fA and fB (That doesn't sound right.)? Do I have the condition statement correct? - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Handling Feature Dependencies
Robert, I encountered this same issue when porting our installer from InstallShield to WiX. InstallShield has the ability to make dependencies between features - I decompiled the MSI and discovered that it does it with a custom action and a custom table of dependencies called ISRequiredFeature. It is not too hard to write a similar custom action that reads records from a custom table and enables the subordinate features as required. I run my custom action just before InstallValidate. 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. Regards, John _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 15 October 2007 17:06 To: wix-users@lists.sourceforge.net 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 installed if fA or fB is installed. If neither of those gets installed, fC should not be installed. Now what the seemingly obvious answer is, is to add a condition to fC on the order of: Feature Id=fA Level=1 /Feature Feature Id=fB Level=1 /Feature Feature Id=fC Level=0 Display=hidden Condition Level=1![CDATA[ (fA = 3) OR (fB = 3)]]/Condition /Feature But that does not seem to work. What am I missing? Is this not the proper way to evaluate a Feature condition that is based on the selection of other features. Can I not do the evaluation of the condition in fC in the FileCost action since the feature selection is there? Can I make fC a sub-feature of both fA and fB (That doesn't sound right.)? Do I have the condition statement correct? - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
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/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
