ndows Installer XML toolset."
Subject: Re: [WiX-users] Custom Action Condition Table
Better to write your CustomActions to be data driven and use Component
states to control when things get installed. That's what the WiX custom
actions do so there is plenty of example code.
On Th
Better to write your CustomActions to be data driven and use Component
states to control when things get installed. That's what the WiX custom
actions do so there is plenty of example code.
On Thu, Feb 2, 2012 at 8:05 PM, Amit Khurana wrote:
> Yes. But I don't want to include these files. I woul
Yes. But I don't want to include these files. I would like to see simple
chart which use these properties e.g. REMOVE="ALL", Installed, NOT
Upgrading, NOT Uninstalling AND NOT UPGRADINGPRODUCTCODE and tell me where
they are applicable. But I think I'll try to get that information from this
link tha
These?
http://code.dblock.org/msi-property-patterns-upgrading-firstinstall-and-maint
enance
-Original Message-
From: Amit Khurana [mailto:amit.khur...@gmail.com]
Sent: 02 February 2012 11:19
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Custom Action Condition Table
Can
Can somebody provide with the table that can show which conditions to use for
Custom Actions to run only on Install only, Install and Modify, Modify
only and Uninstall only?
Thanks in advance.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Custo
5 matches
Mail list logo