Neil Sleightholm wrote:
>
> Where do you have RemoveExistingProducts scheduled? Have you tried it
> after InstallValidate so that is removes everything before reinstalling.
>
> Neil
>
> Neil Sleightholm
> X2 Systems Limited
> n...@x2systems.com <mailto:n...@x2systems.com>
>
>
> ________________________________
>
> From: Adam Burton [mailto:adz...@googlemail.com]
> Sent: Mon 09/02/2009 13:08
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] COM Plus Applications and Major Upgrade
>
> Hi,
> I have been working on an installer for a COM application. The installer
> contains a few .NET assemblies, with a couple configuration files and
> installs a COM application that uses the .NET assemblies (with the
> ComPlusExtension). Due to our development not being so strict I figured it
> would probably be easier if each install was a major upgrade than messing
> with minor and small. So to test this I generated the MSI and installed,
> all
> is well so far. Next I changed the product guid (ok well actually I had it
> set to '*' :-) ) and increased the version from 2.0.0.0 to 2.1.0.0 (both
> the
> steps I believe are required to initiate a major upgrade). I generated the
> MSI and attempted an install. During the install the installation
> complained
> a COM application with the specified id already existed, retry had no
> effect, so I tried ignore and the install completed successfully. I tried
> minor and small updates afterward just to confirm and they did not
> complain.
> So is there something I am missing when it comes to major upgrades and the
> ComPlusExtension? Or even just something I am missing with Major Upgrades
> in
> general?
>
> I tried this again 3.0.4805.0 and 3.0.5006.0, same result.
>
> Cheers,
> Adam
> ------------------------------------------------------------------------------
>
I also do Major upgrades *all* the time. We have a large COM, COM+, VB6
application and I don't dare play games with COM+ registries as I value my
time too much :P It's a requirement for us developers to move back and
forth along the versions and I want to force uninstall our product
regardless what version is installed.
1. I remove the product after InstallFinalize. This has worked for me for
about 2 years now using WiX 2.0 and 3.0.
<InstallExecuteSequence>
<RemoveExistingProducts
After="InstallFinalize"><![CDATA[PREVIOUSVERSIONFOUND]]><RemoveExistingProducts>
</InstallExecuteSequence>
2. I set the version in the upgrade element as following:
<Upgrade Id="C4130B7E-C5F6-4C8D-8806-85D41DB873DC">
<UpgradeVersion IncludeMinimum="yes" Minimum="0.0.0.0"
property="PREVIOUSVERSIONFOUND" />
</Upgrade>
Please note that the above will produce a warning in light - ICE61
(http://msdn.microsoft.com/en-us/library/aa369005(VS.85).aspx). I'm fully
aware that by not setting a Maximum, and putting the minimum at 0, I ensure
*all* versions are detected as previous versions and are uninstalled.
You can use suppress this warning in command line interface option for
light.
Roy
--
View this message in context:
http://n2.nabble.com/COM-Plus-Applications-and-Major-Upgrade-tp2297098p2376186.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
