Thanks to all who responded.
 
I ended up writing a little bit of code to look up the installed product
code in the registry by the product name and then spawn msiexec /x with
that.
PS to save headache just use the reg apis, the wmi ones work but the
installed products search even scoped to local machine took ~3 min to
return results..

________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of LEMIRE,
JOHN
Sent: Wednesday, July 25, 2007 6:52 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to automated uninstall?


I'm wondering if anyone's run into this before and has a "best practice"
solution.
 
The scenario is an automated deployment environment that attempts to run
a scheduled upgrade of minor revisions of a product.
Therefore the numbers of the currently installed and to be installed
versions only differ in the revision position.
The major/minor/build positions are identical. This leads msi to not
perform the install as it only looks as far as build to determine
difference.
 
The first reaction to get around this is to try uninstall/reinstall
instead of upgrade, however uninstall seems to require either the
original msi file (no longer present) or the ProductCode.
 
Being a good wix citizen I have set my <Product Id="*" .../> which means
new ProductCode for every build and makes it hard to script uninstall by
ProductCode.
Is there a way to achieve the unistall that I'm overlooking? Getting the
build portion of the version number changed is beyond my control and
even new minor revisions do need to be deployed for testing.
 
thanks
-john
 

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to