And the command line reinstall is where there's a major problem from an end user perspective. There's no way that I can convince users to run with a command line, so there needs to be some way to force the msi engine to run with those parameters. So far, I see a couple of options:
-I'm already using the MSBUILD bootstrapper for .net, but there doesn't seem to be any way to tell it to set REINSTALL and INSTALLMODE. If anyone knows how to do this, it'd be greatly appreciated. -Write my own bootstrapper. This would certainly take more time than I planned for this install project. -Force all upgrades to be major-Other than performance, is there any reason that this is a bad idea? Our apps are reasonably small, so it shouldn't take all that long, but I understand that in principle this is a bad idea. -Use an SFX archive-I already distribute my installers in an SFX archive (to package the msi and bootstrapper), so theoretically I should be able to have the SFX run setup.exe with the parameters. Unfortunately, my ZIP to SFX conversion tool doesn't seem to support command line parameters either. Does anyone know of a free command line tool to convert a .zip file to a self extracting exe that supports auto extraction and execution? There has to be a way to deal with this, doesn't there? Chris -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wilson, Phil Sent: Tuesday, March 27, 2007 2:47 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Another version of this product is already installed Minor upgrades need a command line install: msiec /i <path to msi file> REINSTALL=ALL REINSTALLMODE=vomus would be a typical command line. A major upgrade requires a ProductCode change, identical UpgradeCode to the older version, plus entries in the Upgrade table. Major upgrades are unfortunately more of an intent than an actual declaration. If you don't get all the plumbing right you'll end up with two versions of the product on the system. Minor upgrades tell you upfront that you're not doing the right thing ("another version is installed"). Phil Wilson ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, March 27, 2007 10:57 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Another version of this product is already installed I'm trying to come to grips with how upgrades are handled, and I was wondering if someone could shed some light on the subject for me. In an attempt to understand better, I've been trying to install a pseudo "minor upgrade". I installed the base version, then I tried to install the slightly modified "upgrade" version. I changed: Product Version attribute. Package Id (auto generated) The contents of one text file. I left unchanged: Everything else, including Product Id & UpgradeCode Each time I've tried, I get the "Another version of this product is already installed" dialog. What gives? ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE V _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
