Something strange here: you say that PREVFOUND is in the Upgrade table for
the initial version, and different properties are in the Upgrade table for
the newer one. Yet the section of the log showing the parsing of the Upgrade
table says:
FindRelatedProducts: Found application:
{C0C6FEAB-9024-481E-BB4F-7A54EC0BA765}
MSI (c) (C8:A0) [15:29:09:708]: PROPERTY CHANGE: Adding PREVFOUND property.
Its value is '{C0C6FEAB-9024-481E-BB4F-7A54EC0BA765}'.
That suggests that the "newer" MSI isnt the one used in your attempt.
-----Original Message-----
From: fiordean dacian [mailto:dfiord...@yahoo.com]
Sent: Saturday, September 25, 2010 4:41 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Major upgrade, MigrateFeatureStates & custom action
Hi Phil, thanks. Actually I wanted it that way, but I feel it's not the
problem at the moment.
Yet, as is my case, 2 features and the original installer installed
Feature1, I would like the upgrade to go directly upgrading the installed
feature with no UI displayed to select what feature to install (ie go on and
upgrade Feature1). As far as I understand it, scheduling
MigrateFeatureStates will set the feature status of the new installer as
found in the original installer (ie my UI for the new installer will
preselect the currently installed feature but still let the user specify
what it wants by actually displaying the UI). Now there might be a problem
indeed. The UI I'm using for my installer is a list box I populate within a
custom action (within a DLL) but actually not query for feature state in
that custom action and preselect anything (I was somehow expecting the MSI
to do it, but of course that's stupid).
Now back to my problem, can you see any problem in the log I posted below or
is the fact that I'm using a UI and schedule MigrateFeatureStates which
creates me problems?
Thanks in advance.
--- On Fri, 9/24/10, Wilson, Phil <phil.wil...@invensys.com> wrote:
From: Wilson, Phil <phil.wil...@invensys.com>
Subject: Re: [WiX-users] Major upgrade, MigrateFeatureStates & custom action
To: "General discussion for Windows Installer XML toolset."
<wix-users@lists.sourceforge.net>
Date: Friday, September 24, 2010, 8:01 PM
Setting MigrateFeatureStates means that you want to do an upgrade where the
features that get installed are exactly the same as the features that are
already installed. It usually doesn't make sense to set that and then set
features in a UI dialog.
Phil Wilson
-----Original Message-----
From: fiordean dacian [mailto:dfiord...@yahoo.com]
Sent: Friday, September 24, 2010 8:01 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Major upgrade, MigrateFeatureStates & custom action
Hi
I made a mistake when I copied the "FindRelatedProducts" in my initial
email. Here is the correct text from the verbose log (we see the property
WIX_UPGRADE_DETECTED being correctly set to my initial installed product
GUID)
Action start 16:44:52: FindRelatedProducts.
FindRelatedProducts: Found application:
{C0C6FEAB-9024-481E-BB4F-7A54EC0BA765}
MSI (c) (38:4C) [16:44:52:289]: PROPERTY CHANGE: Adding WIX_UPGRADE_DETECTED
property. Its value is '{C0C6FEAB-9024-481E-BB4F-7A54EC0BA765}'.
MSI (c) (38:4C) [16:44:52:289]: PROPERTY CHANGE: Adding MIGRATE property.
Its value is '{C0C6FEAB-9024-481E-BB4F-7A54EC0BA765}'.
Action ended 16:44:52: FindRelatedProducts. Return value 1.
Thanks.
--- On Fri, 9/24/10, fiordean dacian <dfiord...@yahoo.com> wrote:
From: fiordean dacian <dfiord...@yahoo.com>
Subject: Major upgrade, MigrateFeatureStates & custom action
To: wix-users@lists.sourceforge.net
Date: Friday, September 24, 2010, 5:39 PM
Hello
I have a couple of problems with my installer on a major upgrade. I'm using
Wix 3.5.
My installer has 2 features and I use the MajorUpgrade element available
with Wix 3.5 to do my major upgrade.
Here is what I did:
Product Code and version changed within the new installer.
As I use "MajorUpgrade" element, I removed my explicit declaration of
RemovedExistingProducts as "MajorUpgrade" seems it schedules it. From the
documentation, I understand "MajorUpgrade" schedules also
MigrateFeatureStates and this is good as I want to take advantage of this
MSI feature (more below).
ALLUSERS property is set to 1 in both installers.
Here is what I get:
Install the first version of the product which installs fine; then launch
the installer for the newer version to perform an upgrade.
I do a verbose log and I get a
couple of strange things:
Action 15:29:09: FindRelatedProducts. Searching for related applications
Action start 15:29:09: FindRelatedProducts.
FindRelatedProducts: Found application:
{C0C6FEAB-9024-481E-BB4F-7A54EC0BA765}
MSI (c) (C8:A0) [15:29:09:708]: PROPERTY CHANGE: Adding PREVFOUND property.
Its value is '{C0C6FEAB-9024-481E-BB4F-7A54EC0BA765}'.
Action ended 15:29:09: FindRelatedProducts. Return value 1.
...
MSI (c) (C8:A0) [15:29:09:817]: Doing action: MigrateFeatureStates
Action 15:29:09: MigrateFeatureStates. Migrating feature states from related
applications
Action start 15:29:09: MigrateFeatureStates.
Action ended 15:29:09: MigrateFeatureStates. Return value 0.
...
Plenty of
Disallowing installation of component:
{83D1BFA5-5703-43F2-AB56-BB0630B8E921} since the same component with higher
versioned keyfile exists
...
My 2 features are absent from the installation
MSI (s) (5C:FC) [15:29:23:721]: Feature: FullInstallation; Installed:
Absent; Request: Null; Action: Null
MSI (s) (5C:FC) [15:29:23:721]: Feature: DcServer; Installed: Absent;
Request: Null; Action: Null
This explains why no upgrade is done, the question is why they are absent? I
select them through a UI which changed like below compared to the previous
version of my installer:
Old version:
<InstallUISequence>
<Custom Action="FillingListBox" After="CostFinalize" />
</InstallUISequence>
New version:
<InstallUISequence>
<Custom Action="FillingListBox" After="MigrateFeatureStates" />
</InstallUISequence>
Nothing is removed like for a major upgrade (and it says this is
maintainance or uninstall):
MSI (s) (5C:FC) [15:29:23:736]: Doing action: RemoveExistingProducts
Action 15:29:23: RemoveExistingProducts. Removing applications
Action start 15:29:23: RemoveExistingProducts.
MSI (s) (5C:FC) [15:29:23:736]: Skipping RemoveExistingProducts action:
current configuration
is maintenance mode or an uninstall
Action ended 15:29:23: RemoveExistingProducts. Return value 0.
So it looks like MigrateFeatureStates doesn't detect the feature state of
the current installation to set it for the new version of the installer.
Here is the Upgrade table for the initial installer:
Upgrade code
Version Attributes ActionProperty
{CB09E96B-19D6-439C-9A40-68143559032A} 6.6.0 258
NEWERFOUND
{64EF24E1-8FC8-44C0-B9AD-981D638B4596} 6.5.0 6.6.0 256
PREVFOUND
And here is the Upgrade table for the new installer:
{CB09E96B-19D6-439C-9A40-68143559032A} 6.7.0 1 WIX_UPGRADE_DETECTED
{CB09E96B-19D6-439C-9A40-68143559032A} 6.7.0 2 WIX_DOWNGRADE_DETECTED
Anyone has an idea what am I doing wrong?
Thanks!
----------------------------------------------------------------------------
--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
*** Confidentiality Notice: This e-mail, including any associated or
attached files, is intended solely for the individual or entity to which it
is addressed. This e-mail is confidential and may well also be legally
privileged. If you have received it in error, you are on notice of its
status. Please notify the sender immediately by reply e-mail and then delete
this message from your system. Please do not copy it or use it for any
purposes, or disclose its contents to any other person. This email comes
from a division of the Invensys Group, owned by Invensys plc, which is a
company registered in England and Wales with its registered office at 3rd
Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For
a list of European legal entities within the Invensys Group, please go to
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77
.
You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
recept...@invensys.com. This e-mail and any attachments thereto may be
subject to the terms of any agreements between Invensys (and/or its
subsidiaries and affiliates) and the recipient (and/or its subsidiaries and
affiliates).
----------------------------------------------------------------------------
--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------------
--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
