WSE30 is not set, log file does not show the property at all, FindRelated is before LauchConditions. Seems to be a WSE problem, I searched the registry for the upgrade code and it's not there (?) I will try with another product, and will try also ComponentSearch.
On Wed, Jan 28, 2009 at 6:36 PM, Christopher Painter < chr...@deploymentengineering.com> wrote: > I'd look at the logfile and built MSI using ORCA and see what's going on. > Is FindRelatedProduts sequenced/running prior to LaunchConditions? Is > FindRelatedProperty setting the WSE30 property with a found product code. > > Christopher Painter, Author of Deployment Engineering Blog > Have a hot tip, know a secret or read a really good thread that deserves > attention? E-Mail Me > > > --- On Wed, 1/28/09, Eitan Behar <ei...@baconao.net> wrote: > > > From: Eitan Behar <ei...@baconao.net> > > Subject: Re: [WiX-users] Detecting if a product is installed and setting > property > > To: chr...@deploymentengineering.com, "General discussion for Windows > Installer XML toolset." <wix-users@lists.sourceforge.net> > > Date: Wednesday, January 28, 2009, 9:57 AM > > sounds great, but, it does not seem to work :^( > > > > I have the code below, and although WSE is installed, I > > keep getting the > > Condition Message. I have checked the msi which I used to > > install WSE and > > the Upgrade Code is correct. (I did copy-paste from its > > msi) > > > > <Upgrade > > Id="B4BB35AA-51EC-41A5-9C85-90D6FA98968C"> > > <UpgradeVersion Maximum="99.0.0.0" > > Property="WSE30" OnlyDetect="yes" > > ExcludeLanguages="yes"/> > > </Upgrade> > > > > <Property Id="WSE30" > > Secure="yes"/> > > > > <Condition Message="This application requires WSE > > 3.0. Please install WSE > > 3.0 then run this installer again."> > > <![CDATA[Installed OR WSE30]]> > > </Condition> > > > > <InstallExecuteSequence> > > <FindRelatedProducts Before="LaunchConditions" > > /> > > </InstallExecuteSequence> > > > > On Wed, Jan 28, 2009 at 4:25 PM, Christopher Painter < > > chr...@deploymentengineering.com> wrote: > > > > > As much as I love DTF, I don't see the need for a > > CA in this scenario. I > > > believe you stated that the requirement is to detect > > products installed > > > based on their upgrade code and block the install if a > > product is not > > > detected. > > > > > > If that is correct, then the Upgrade table supports > > the > > > msidbUpgradeAttributesOnlyDetect attribute which > > allows you to do your > > > search, put found product codes into the property > > specified in the > > > ActionProperty column. As long as you schedule > > FindRelatedProducts prior > > > to Launch Conditions, you could then use the above > > property as a conditional > > > expression to block your install. > > > > > > Christopher Painter, Author of Deployment Engineering > > Blog > > > Have a hot tip, know a secret or read a really good > > thread that deserves > > > attention? E-Mail Me > > > > > > > > > --- On Wed, 1/28/09, Eitan Behar > > <ei...@baconao.net> wrote: > > > > > > > From: Eitan Behar <ei...@baconao.net> > > > > Subject: Re: [WiX-users] Detecting if a product > > is installed and setting > > > property > > > > To: "General discussion for Windows > > Installer XML toolset." < > > > wix-users@lists.sourceforge.net> > > > > Date: Wednesday, January 28, 2009, 8:04 AM > > > > Thanks ! Sounds like I will use a DTF CA for > > that. > > > > > > > > > > > > > > > > > > > > On Wed, Jan 28, 2009 at 3:21 PM, Yan Sklyarenko > > > > <y...@sitecore.net> wrote: > > > > > > > > > If your product is the same family as those > > you're > > > > detecting, then you > > > > > might take advantage of FindRelatedProducts > > action: > > > > > > > http://msdn.microsoft.com/en-us/library/aa368600.aspx. > > > > > This is supported in WiX toolset via > > UpgradeVersion > > > > element, which > > > > > actually maps to the Upgrade MSI table, and > > > > FindRelatedProducts element, > > > > > which is there for sequencing purpose, as > > far as I can > > > > see (never used > > > > > it myself yet). > > > > > > > > > > If otherwise your product has nothing in > > common with > > > > those you'd like to > > > > > detect, then it might require custom action. > > DTF > > > > contains a class > > > > > ProductInstallation, which defines a method > > > > > GetRelatedProducts(upgradeCode), it's > > probably > > > > what you need (if your > > > > > installation is compatible with managed > > custom > > > > actions). > > > > > That's just an assumption, there might > > be better > > > > techniques for this. > > > > > > > > > > Hope this helps. > > > > > > > > > > -- Yan > > > > > > > > > > -----Original Message----- > > > > > From: Eitan Behar [mailto:ei...@baconao.net] > > > > > Sent: Wednesday, January 28, 2009 10:14 AM > > > > > To: General discussion for Windows Installer > > XML > > > > toolset. > > > > > Subject: [WiX-users] Detecting if a product > > is > > > > installed and setting > > > > > property > > > > > > > > > > Hi, > > > > > > > > > > Is there a way to detect if a product family > > is > > > > installed according to > > > > > its > > > > > product code, and set a property > > accordingly? I need > > > > to stop the setup > > > > > if > > > > > certain products are not installed, and I > > only have > > > > their upgrade codes, > > > > > not > > > > > the product code. > > > > > > > > > > Thanks, > > > > > > > > > > Eitan > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > ------ > > > > > This SF.net email is sponsored by: > > > > > SourcForge Community > > > > > SourceForge wants to tell your story. > > > > > http://p.sf.net/sfu/sf-spreadtheword > > > > > > > _______________________________________________ > > > > > WiX-users mailing list > > > > > WiX-users@lists.sourceforge.net > > > > > > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > > > This SF.net email is sponsored by: > > > > > SourcForge Community > > > > > SourceForge wants to tell your story. > > > > > http://p.sf.net/sfu/sf-spreadtheword > > > > > > > _______________________________________________ > > > > > WiX-users mailing list > > > > > WiX-users@lists.sourceforge.net > > > > > > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > > This SF.net email is sponsored by: > > > > SourcForge Community > > > > SourceForge wants to tell your story. > > > > http://p.sf.net/sfu/sf-spreadtheword > > > > _______________________________________________ > > > > WiX-users mailing list > > > > WiX-users@lists.sourceforge.net > > > > > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > This SF.net email is sponsored by: > > > SourcForge Community > > > SourceForge wants to tell your story. > > > http://p.sf.net/sfu/sf-spreadtheword > > > _______________________________________________ > > > WiX-users mailing list > > > WiX-users@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
