Yes, the installer found the related product:
MSI (c) (A0:08) [11:20:08:562]: Doing action: FindRelatedProducts
MSI (c) (A0:08) [11:20:08:562]: Note: 1: 2205 2: 3: ActionText
Action 11:20:08: FindRelatedProducts. Searching for related applications
Action start 11:20:08: FindRelatedProducts.
FindRelatedProducts: Found application:
{2779B856-ED76-470B-BD81-CD9FC9FA4ABC}
MSI (c) (A0:08) [11:20:08:578]: PROPERTY CHANGE: Adding
NEWERVERSIONDETECTED property. Its value is
'{2779B856-ED76-470B-BD81-CD9FC9FA4ABC}'.
Action ended 11:20:08: FindRelatedProducts. Return value 1.
On 3/08/2010 10:22 a.m., Christopher Painter wrote:
> What does the log say? Does FindRelatedProducts find the product and set the
> property? One common problem is a Major Upgrade can go from a Per-User to
> Per-Machine install or the other way around.
>
> 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
>
>
>
> ----- Original Message ----
> From: Joe Osman<joe.os...@taitradio.com>
> To: wix-users@lists.sourceforge.net
> Sent: Mon, August 2, 2010 4:40:24 PM
> Subject: Re: [WiX-users] Does WIX / MSI support product downgrade - still
> doesn't work
>
> I followed your suggestions and scheduled the remove existing products
> before InstalInitialize but it's still doesn't work. The old version
> gets installed beside the new version and it doesn't remove it. When I
> tried to schedule the product removal before CostInitialize I got a
> compilation error.
>
> Here is the sample project:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";>
> <Product Id="*"
> Name="WixProject1 $(var.Version)"
> Language="1033"
> Version="$(var.Version)"
> Manufacturer="WixProject1"
> UpgradeCode="56e0b99a-fb15-45ac-ad83-9e2376e69744">
> <Package InstallerVersion="200" Compressed="yes" />
>
> <Media Id="1" Cabinet="media1.cab" EmbedCab="yes" />
>
> <Upgrade Id="56e0b99a-fb15-45ac-ad83-9e2376e69744">
> <UpgradeVersion Minimum="$(var.Version)"
> OnlyDetect="yes"
> IncludeMinimum="no"
> Property="NEWERVERSIONDETECTED" />
> <UpgradeVersion Minimum="0.0.0"
> Maximum="$(var.Version)"
> IncludeMinimum="yes"
> IncludeMaximum="no"
> Property="OLDERVERSIONBEINGUPGRADED" />
> </Upgrade>
>
> <Feature Id="Feature1" Level="1" ConfigurableDirectory="INSTALLDIR"
> Description="Create new folder" Title="Create new folder">
> <ComponentRef Id="CreateNewFolder"/>
> <ComponentRef Id ="File1"/>
> </Feature>
>
> <Directory Id="TARGETDIR" Name="SourceDir">
> <Directory Id="DataBaseFolder">
> <Component Id="CreateNewFolder"
> Guid="{4C1F68DD-11F4-4fc1-B494-DEBB52CEDA96}">
> <CreateFolder/>
> </Component>
> <Directory Id="INSTALLDIR">
> <Component Id="File1" DiskId="1" KeyPath="yes"
> Guid="3FC72951-D247-4959-9908-4308E77D0218">
> <File Id="temp.txt" Source=".\temp1.txt" />
> </Component>
> </Directory>
> </Directory>
> </Directory>
>
> <InstallExecuteSequence>
> <RemoveExistingProducts Before="InstallInitialize" />
> </InstallExecuteSequence>
>
> </Product>
> </Wix>
>
>
> On 3/08/2010 1:09 a.m., Christopher Painter wrote:
>
>> When I worked at Continental Airlines I would always schedule
>> RemoveExistingProducts prior to CostInitialize. I was pushing my packages
>>
> with
>
>> SMS as System so I wasn't concerned with elevation concerns. I wanted my
>> installs to behave as close as possible to an uninstall / reinstall because
>>
> our
>
>> roll back strategy in case of application problems was to readvertise
>> the package for the previous version.
>>
>> 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
>>
>>
>>
>> ----- Original Message ----
>> From: Rob Hamflett<r...@snsys.com>
>> To: wix-users@lists.sourceforge.net
>> Sent: Mon, August 2, 2010 7:03:37 AM
>> Subject: Re: [WiX-users] Does WIX / MSI support product downgrade ?
>>
>> For years I used to have RemoveExistingProducts scheduled before
>> CostInitialize,
>> and then a few
>>
>> weeks ago msiexec started crashing on some customers machines. When I moved
>> RemoveExistingProducts
>>
>> to after InstallInitialize everything started working again.
>>
>> Rob
>>
>> On 02/08/2010 11:56, Pally Sandher wrote:
>>
>>
>>> You could achieve that by simply scheduling RemoveExistingProducts
>>> before InstallInitialize ->
>>> http://msdn.microsoft.com/en-us/library/aa371197(VS.85).aspx. "normal"
>>> usage placement tends to be after InstallInitialize as the WiX
>>> documentation suggests ->
>>> http://wix.sourceforge.net/manual-wix3/major_upgrade.htm but it also
>>> mentions reviewing the placement options as above.
>>>
>>> Palbinder Sandher
>>> Software Deployment& IT Administrator
>>> T: +44 (0) 141 945 8500
>>> F: +44 (0) 141 945 8501
>>>
>>> http://www.iesve.com
>>> **Design, Simulate + Innovate with the<Virtual Environment>**
>>> Integrated Environmental Solutions Limited. Registered in Scotland No.
>>> SC151456
>>> Registered Office - Helix Building, West Of Scotland Science Park,
>>> Glasgow G20 0SP
>>> Email Disclaimer
>>>
>>> -----Original Message-----
>>> From: Rob Hamflett [mailto:r...@snsys.com]
>>> Sent: 02 August 2010 08:52
>>> To: wix-users@lists.sourceforge.net
>>> Subject: Re: [WiX-users] Does WIX / MSI support product downgrade ?
>>>
>>> > Does Wix / MSI support product downgrade ?
>>>
>>> Sort of, but not fully. You can schedule RemoveExistingProducts after
>>> InstallInitialize to remove the old version before installing the new
>>> version. By this point though the costing has already happened so
>>> Windows Installer has already decided what it thinks needs to be done
>>> with the files, despite the fact that RemoveExistingProducts changes all
>>> that. You can specify the REINSTALLMODE property to have the value
>>> "amus" which will force the files from the installer you're running to
>>> overwrite any existing ones. This is needed to make sure that files get
>>> downgraded to the lower versions your older install will be carrying.
>>> This is only safe though if you have no shared components. In this case
>>> you'll need to uninstall the existing version via some other method
>>> (i.e.
>>> a bootstrapper) before installing the new/old one.
>>>
>>> Rob
>>>
>>>
>>> ------------------------------------------------------------------------
>>> ------
>>> The Palm PDK Hot Apps Program offers developers who use the Plug-In
>>> Development Kit to bring their C/C++ apps to Palm for a share of $1
>>> Million in cash or HP Products. Visit us here for more details:
>>> http://p.sf.net/sfu/dev2dev-palm
>>> _______________________________________________
>>> WiX-users mailing list
>>> WiX-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>>
>>>
>>>
>>>
>>>
> ------------------------------------------------------------------------------
>
>>> The Palm PDK Hot Apps Program offers developers who use the
>>> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
>>> of $1 Million in cash or HP Products. Visit us here for more details:
>>> http://p.sf.net/sfu/dev2dev-palm
>>>
>>>
>> ------------------------------------------------------------------------------
>> The Palm PDK Hot Apps Program offers developers who use the
>> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
>> of $1 Million in cash or HP Products. Visit us here for more details:
>> http://p.sf.net/sfu/dev2dev-palm
>> _______________________________________________
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> The Palm PDK Hot Apps Program offers developers who use the
>> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
>> of $1 Million in cash or HP Products. Visit us here for more details:
>> http://p.sf.net/sfu/dev2dev-palm
>> _______________________________________________
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>>
>
--
Joe Osman
Design Engineer
Tait Radio Communications
175 Roydvale Avenue Christchurch
New Zealand
DDI: 64 3 3571584
www.taitradio.com
joe.os...@taitradio.com
TAIT: THE RIGHT FIT
=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
=======================================================================
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
