Re: [WiX-users] Feature element - Condition nightmare
Finally, the light at the end of the tunnel As I expected, turns out I used the FileSearch incorrectly. Unfortunatelly, the WiX / MSI docs are misleading - or better said, the MSI docs are pretty much almost impossible to use and understand from the first read :)). The fact that FileSearch is presented as a posible child of Property is a bit unfortunate... It has to be a child of DirectorySearch to get expected results. Here is the code that DOES work as I intended: - Original Message From: Adrian Gantoi <[EMAIL PROTECTED]> To: Alexei <[EMAIL PROTECTED]>; wix-users@lists.sourceforge.net Sent: Friday, August 17, 2007 9:52:12 AM Subject: Re: [WiX-users] Feature element - Condition nightmare No , it still does not work as I intend. Is it possible to use FileSearch to set a property used in a Condition for a Feature or I started on the wrong road ? - Original Message From: Alexei <[EMAIL PROTECTED]> To: wix-users@lists.sourceforge.net Sent: Thursday, August 16, 2007 2:44:59 PM Subject: Re: [WiX-users] Feature element - Condition nightmare Adrian, I haven't tried this but what I would do is when you declare your Property - omit the Value attribute. This way the property will be undefined. Then when you are checking use something like: <[FOUNDTABCTL32]> This way when the FileSearch finds something then [FOUNDTABCTL32] will be defined and the condition will hold, thereby setting the FeatureToInstallWhenOCXMissing Level="0" Tell me if this helps at all, Alexei Adrian Gantoi wrote: > > Hi all, > > I'm having a problem with correctly specifying the Feature's Condition. > My goal - make a search of an ocx file, and if the ocx file does not exist > on the target computer, > keep a feature selected for installation. > If the ocx exists, the feature should be automatically deselected. > I'm currently having doubts if this is possible, since FileSearch should > return a string... > My code below: > > > > > > >Level="1"> > > > > > > Am I doing something wrong or this is not possible ? > > Thanks for any help, > Adrian > -- View this message in context: http://www.nabble.com/Feature-element---Condition-nightmare-tf4279047.html#a12179726 Sent from the wix-users mailing list archive at Nabble.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 Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. http://tv.yahoo.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
Re: [WiX-users] Feature element - Condition nightmare
No , it still does not work as I intend. Is it possible to use FileSearch to set a property used in a Condition for a Feature or I started on the wrong road ? - Original Message From: Alexei <[EMAIL PROTECTED]> To: wix-users@lists.sourceforge.net Sent: Thursday, August 16, 2007 2:44:59 PM Subject: Re: [WiX-users] Feature element - Condition nightmare Adrian, I haven't tried this but what I would do is when you declare your Property - omit the Value attribute. This way the property will be undefined. Then when you are checking use something like: <[FOUNDTABCTL32]> This way when the FileSearch finds something then [FOUNDTABCTL32] will be defined and the condition will hold, thereby setting the FeatureToInstallWhenOCXMissing Level="0" Tell me if this helps at all, Alexei Adrian Gantoi wrote: > > Hi all, > > I'm having a problem with correctly specifying the Feature's Condition. > My goal - make a search of an ocx file, and if the ocx file does not exist > on the target computer, > keep a feature selected for installation. > If the ocx exists, the feature should be automatically deselected. > I'm currently having doubts if this is possible, since FileSearch should > return a string... > My code below: > > > > > > >Level="1"> > > > > > > Am I doing something wrong or this is not possible ? > > Thanks for any help, > Adrian > -- View this message in context: http://www.nabble.com/Feature-element---Condition-nightmare-tf4279047.html#a12179726 Sent from the wix-users mailing list archive at Nabble.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 Pinpoint customers who are looking for what you sell. http://searchmarketing.yahoo.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
Re: [WiX-users] Feature element - Condition nightmare
Adrian, I haven't tried this but what I would do is when you declare your Property - omit the Value attribute. This way the property will be undefined. Then when you are checking use something like: <[FOUNDTABCTL32]> This way when the FileSearch finds something then [FOUNDTABCTL32] will be defined and the condition will hold, thereby setting the FeatureToInstallWhenOCXMissing Level="0" Tell me if this helps at all, Alexei Adrian Gantoi wrote: > > Hi all, > > I'm having a problem with correctly specifying the Feature's Condition. > My goal - make a search of an ocx file, and if the ocx file does not exist > on the target computer, > keep a feature selected for installation. > If the ocx exists, the feature should be automatically deselected. > I'm currently having doubts if this is possible, since FileSearch should > return a string... > My code below: > > > > > > >Level="1"> > > > > > > Am I doing something wrong or this is not possible ? > > Thanks for any help, > Adrian > -- View this message in context: http://www.nabble.com/Feature-element---Condition-nightmare-tf4279047.html#a12179726 Sent from the wix-users mailing list archive at Nabble.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] Feature element - Condition nightmare
Hi all, I'm having a problem with correctly specifying the Feature's Condition. My goal - make a search of an ocx file, and if the ocx file does not exist on the target computer, keep a feature selected for installation. If the ocx exists, the feature should be automatically deselected. I'm currently having doubts if this is possible, since FileSearch should return a string... My code below: Am I doing something wrong or this is not possible ? Thanks for any help, Adrian Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow - 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
