PameAlex wrote:
Another thing kind of curious is the fact that the other
property(OLDAPPFOUND) I am using to avoid the component to be installed
during the Upgrade is working so the issue is only in the uninstallation
part.
You're not going to be able to use component conditions to
The property is being set correctly
Action 17:11:37: RemoveExistingProducts. Removing applications
Action start 17:11:37: RemoveExistingProducts.
RemoveExistingProducts: Application: {D2E3C4E8-F835-42BF-9871-DC2AF481361B},
Command line:
The RemoveExistingProducts action is after FindRelatedProducts
InstallExecuteSequence
Custom Action=NewerVersionDetected
After=FindRelatedProductsNEWAPPFOUND/Custom
Custom Action=RemoveExistingProducts
After=InstallValidateOLDAPPFOUND/Custom
/InstallExecuteSequence
Upgrade
PameAlex wrote:
The RemoveExistingProducts action is after FindRelatedProducts
I don't think you can rely on the UpgradeVersion properties being passed
to the old product. Check a verbose log after RemoveExistingProducts to
see the major upgrade.
--
sig://boB
http://joyofsetup.com/
Pamela Alvarez wrote:
I really need some help!. I made 3 installers (1.0.1.0 - v1, 1.0.2.0
-v2, 1.0.3.0 -v3) each is a full installer and also a major upgrade of
the previous installer.
Where are you scheduling RemoveExistingProducts?
Condition($(var.IIS5) Or $(var.IIS6)) And
Hi Guys,
I really need some help!. I made 3 installers (1.0.1.0 - v1, 1.0.2.0
-v2, 1.0.3.0 -v3) each is a full installer and also a major upgrade of
the previous installer.
As part of my installation I add a virtual Directory for IIS5 and IIS6
as a part of a component(Comp_VirtualDir) and an
6 matches
Mail list logo
