Subject: Fw: EnterpriseSMS Wix Installation
Please find attached in word document format the EnterpriseSMS WiX InstaLLer
functionality Report. It just spells out why my installer cannot runt
CAQuietExec Custom Actions which are part of the WiXUtilExtension.dll which is
included as a refereence
Comment [WixUtilExtension]:
Wix Toolset Library and Extension DLL reference to a Wix Project. The Wix
Toolset automatically adds necessary parameters to the Compiler (candle.exe)
and Linker (light.exe) command lines, so as to correctly resolve when building
the project.
Linkage of appropriate
Thank you for confirming what I was slowing starting to realize!
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
-Original Message-
From:
I have a custom action that should only run on uninstall, but not run during
an upgrade. After browsing the list archives and other sites, I came up with
the following:
Custom Action='SetUnDeployParams'
After='MsiUnpublishAssemblies'Installed AND (REMOVE=ALL) AND NOT
(UPGRADEFOUND OR
What happens in 3.x as compared to 2.0 is the following: the extension DLLs
contain, as .net embedded resources, a “bound” wixlib that itself contains the
Binary tags referring to the CA DLL(s) which are further bound inside of the
wixlib itself. Simply by referencing the embedded Binary tag
I can't tell from that which product versions are being referred to, but during
an upgrade there are two things going on - the install of the new incoming
product and the uninstall of the previous outgoing product, and:
UPGRADINGPRODUCTCODE is set in the outgoing product when it is being
Yes, I can see in my log where UPGRADINGPRODUCTCODE and UPGRADEFOUND are
being set to the appropriate GUIDs. What I don't understand is how I can
prevent my CustomAction from being executed when the old outgoing product is
being uninstalled. I only want my CustomAction to execute when an
Looks like this is the ticket:
Installed AND REMOVE=ALL AND NOT UPGRADINGPRODUCTCODE
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CustomAction-on-Uninstall-but-not-upgrade-tp5232029p5232458.html
Sent from the wix-users mailing list archive at
One final note of clarification. When mention is made of referencing an
extension in the WiX toolset, this is what is being referred to: providing
either the path or the name (for those extensions in the same directory as the
tool and/or in the GAC) of the extension as the parameter to the -ext
I'm trying to understand how to install a newer version of a
component that is shared between multiple installers. I can't seem
to find any explanation of this in the docs or via google. If I
missed it, a link would be fantastic.
I have about 30 different installers that all have the same
use condition
(NOT UPGRADINGPRODUCTCODE) AND (REMOVE=ALL)
cge wrote:
I have a custom action that should only run on uninstall, but not run during
an upgrade. After browsing the list archives and other sites, I came up with
the following:
Custom Action='SetUnDeployParams'
11 matches
Mail list logo
