You can identify the msi by searching each MSI for your CA in the execute sequence using msi sql. The sequenced CA should have a signature that you can easily detect (the name of your CA, the target, the wrong condition being parts of the signature).
On second thoughts, this technique is unlikely to work at all on Vista upwards because the CA that changes the v1 MSI will not be elevated. 8$ Thanks that will do it, provided that during the enumeration I can identify the original msi (which is created by our customers, as I'm just shipping a merge module.) I'd imagined using the handle of the currently-running msi (the newer version that's going to run RemoveExistingProducts) to get the identity of the original msi, but maybe that's not possible? -- View this message in context: http://n2.nabble.com/how-to-change-an-installed-package--tp2596131p2600813.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
