Hi Peter,
Thank you for your reply.
I tried to write a major upgrade installer. Change the Product ID in each build
for doing upgrade. Keep the Upgrade ID as UpgradeCode. Add the code as the
tutorial 4.1:
Upgrade Id='8517ae9a-667d-4bd3-9cea-4323be6d7040'
UpgradeVersion
Well check that you have the upgrade code correct, but my guess it
would have something to do with @OnlyDetect=yes being set. From the
v2.x documentation:
OnlyDetect | YesNoType | Set to yes to detect products and
applications but do not uninstall.
Hi John,
Thank you for your help. There is some progess in my Upgrade. It will not
install a new software after I change the OnlyDetect.
I have another question that there is one Custom Action, which should be called
only in the first install. Is it correct if I set it as:
Custom Action=MyCA
NOT UPGRADINGPRODUCTCODE will be true during any run of the installer when you
are not performing an upgrade. This includes remove, repair (and patch) and
first time installation. Is that what you want ? If you only want to run during
first-time installation then use:
not
2009/8/5 Jiang, Chunyan (GE Healthcare) chunyan.ji...@ge.com:
Hi John,
Thank you for your help. There is some progess in my Upgrade. It will not
install a new software after I change the OnlyDetect.
Hmm - does it give an error message?
Sorry, I confused you. I mean the Upgrade works now. It will not install a new
software, instead, it upgrade the old one. :)
-Ursprüngliche Nachricht-
Von: John Ludlow [mailto:john.ludlow...@gmail.com]
Gesendet: Mittwoch, 5. August 2009 11:11
An: General discussion for Windows
Thank you for your reply.
I only want the CA to run for the first time installation. I will try to change
the condition to not Installed and try again.
And I have another custon action, which should be called only in
uninstallation. Is it correct to do it as:
Custom Action=MyCA2
That looks correct. It will run when you are removing the product from the
machine entirely but it wont run when you are removing the old product in order
to upgrade it.
-Original Message-
From: Jiang, Chunyan (GE Healthcare) [mailto:chunyan.ji...@ge.com]
Sent: 05 August 2009 10:21
To:
Easily done :)
Glad it's sorted anyway.
John
2009/8/5 Jiang, Chunyan (GE Healthcare) chunyan.ji...@ge.com:
Sorry, I confused you. I mean the Upgrade works now. It will not install a
new software, instead, it upgrade the old one. :)
-Ursprüngliche Nachricht-
Von: John Ludlow
Hi Peter,
I still have the problem about custom action. MyCA is always running during
the Upgrade. I tried the both:
Custom Action=MyCA After=InstallFinalizenot Installed/Custom
and
Custom Action=MyCA After=InstallFinalizenot Installed AND NOT
UPGRADINGPRODUCTCODE/Custom
How can I make MyCA
According to the docs, UPGRADINGPRODUCTCODE is set during a removal.
When I've done this before, I've always used the properties set in the
Upgrade elements - in your case, PATCHFOUND. So maybe try this:
Custom Action=MyCA After=InstallFinalizeNOT Installed AND NOT
PATCHFOUND/Custom
(not sure
According to the docs, UPGRADINGPRODUCTCODE is set during a removal.
When I've done this before, I've always used the properties set in the
Upgrade elements - in your case, PATCHFOUND. So maybe try this:
To clarify - it's set during RemoveExistingProducts,
Hi John,
Thank you for your nice reply.
Unfortunately, MyCA is called again, when I set
Custom Action=MyCA After=InstallFinalizeNOT Installed AND NOT
PATCHFOUND/Custom
How can I stop calling MyCA during Upgrade?
Regards,
Chunyan
-Ursprüngliche Nachricht-
Von: John Ludlow
Hi John,
Thank you.
Could please tell me how to check logs?
-Ursprüngliche Nachricht-
Von: John Ludlow [mailto:john.ludlow...@gmail.com]
Gesendet: Mittwoch, 5. August 2009 14:50
An: General discussion for Windows Installer XML toolset.
Betreff: Re: [WiX-users] How to create the
Hi Yan,
Thank you for your reply. I read the web page as you recommended. It is very
helpful.
I would like to ask whether it is possible to write the first installation and
upgrade in the same msi. The msi shall check if it is new install or upgrade.
If it is upgrade, then do some custom
This article from WiX tutorial should answer your questions:
http://www.tramontana.co.hu/wix/lesson4.php#4.1.
-- Yan
-Original Message-
From: Jiang, Chunyan (GE Healthcare) [mailto:chunyan.ji...@ge.com]
Sent: Tuesday, August 04, 2009 11:52 AM
To: General discussion for Windows
If you write an installer to do a major upgrade, it can be used as a first-time
installer too - theres nothing special you need to do.
To make some custom actions run only when performing a major upgrade and not
during first-time installation, you set the condition of the custom actions to
be
Hi Wix-users,
I have created the installation package with wix. Now I have a new task
that .msi should be upgradable. It means that the newly built .msi
should be installed without uninstalling the last version, when some
files changed in the package.
However, my newly built .msi can not be
First of all, I would encourage you to get acquainted with the resources
below:
- http://msdn.microsoft.com/en-us/library/aa370579(VS.85).aspx and
all descendants - this is essential info about upgrades
- http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/ - a great
summary from Bob
This might also help:
http://neilsleightholm.blogspot.com/2009/01/wix-script-for-major-upgrade
s.html
Neil
-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net]
Sent: 03 August 2009 15:09
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How
20 matches
Mail list logo
