It is done on purpose, because this MSI is specific in the sense, that we use
it launch uninstallation of other MSI components that our product chains -
and those other MSI components are not shown in ARP. What I mean is that we
have just a single entry in ARP for this specific MSI, and when you click to
uninstall it, uninstallation of this MSI starts.
How we proceed is:
1) We clear the REMOVE flag so that this MSI doesn't get uninstalled
automatically when started.
2) And then instead of uninstalling we call a custom action which starts our
EXE application, and this EXE application uninstalls a number of other MSI
packages and finally it also uninstalls this particular MSI.
Our InstallExecuteSequence looks like this:
<InstallExecuteSequence>
<Custom Action="ResetRemove"
Sequence="1">$(var.ConditionChainer)</Custom>
<Custom Action="LaunchMaintenanceChainer"
After="InstallFinalize">$(var.ConditionChainer)</Custom>
</InstallExecuteSequence>
This thing works fine for us if we build the MSI with WiX 3.5, it doesn't
work with WiX 3.6 and WiX 3.7.
Is that something changed in WiX that causes this changed behavior?
Or can you suggest us some other way to achieve what we are about to do?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSI-uninstalls-property-when-built-with-WiX-3-5-fails-with-3-6-and-3-7-tp7584055p7584129.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
