To do that I need to conditionally set the command line arguments with REINSTALLMODE=vomus REINTALL=all when the product is already installed. Does anybody know how to do that using the Visual Studio 2005 GenerateBootstrapper task?
-Matthew Rowan -----Original Message----- From: Stefan Pavlik [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 February 2007 20:29 To: Matthew Rowan Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrapper Hi again... Matthew Rowan wrote: > Thanks for the quick reply Stefan. What I have found is that when I build a > new installer for the next minor version it does not launch in Maintenance > mode because the package code is different, but the product code is the same > and I get the error message "Another version of this product is already > installed. Installation of this version cannot continue....", when using just > the msi or the Visual Studio bootstrapper. > > Do you have your Bootstrapper to always launch with the Reinstall properties > set when the product code is detected to be installed? However, I would have > thought that would always do a reinstall then and not allow maintenance mode. My bootstrapper works in following way: If the product is already installed then the installer is launched with REINSTALLMODE=vomus REINTALL=all So if the package code is the same it will run the Maintenance mode and if the package code is different it will run reinstallation. In fact I do not use the Resume dialog for reinstallation. The Maintenance mode is started in both cases, so the user needs to press the Reinstall (repair) button in order to start reinstallaion. Regards Stefan > > Cheers, > > -Matthew Rowan > > -----Original Message----- > From: Stefan Pavlik [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 14 February 2007 17:24 > To: Matthew Rowan > Cc: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Bootstrapper > > Hi Matthew,... > > I have, personaly, no experience with the Visual Studio > 2005 Bootstrapper but the simple bootstrapper I use (wrote) does not > have the step 6 you are writing about. > It is simply not needed because when you run the maintenance mode > with arguments REINSTALLMODE=vomus REINSTALL=ALL it will do what you > want. It is simply because the 'v' option of REINSTALLMODE means > 'runs from source and recaches local package'. > > Regards > > Stefan > > > Matthew Rowan wrote: >> Hi All, >> >> I know this topic has been of much discussion and I have looked through all >> of the previous mailings but am still unable to produce what I need. All I >> want is a bootstrapper that is similar to InstallShield to perform minor >> upgrades. >> >> I need to: >> 1. Ensure prerequisites are present and if not then install (.NET 2.0, >> Windows Installer 3.1) >> 2. Get the product code of the package. >> 3. Check if the product code is already installed. >> 4. If it isn't, launch the install normally. >> 5. If it is and the package code is the same, launch maintenance mode. >> 6. If the package code is different, launch the install in reinstall mode. >> Preferably I would like to display a splash screen while the bootstrapper >> fires up msiexec. >> >> Almost all the requirements are handled very nicely by the Visual Studio >> 2005 GenerateBootstrapper task and is the preferred solution, however it >> does not handle requirement 6. Changing the product code would resolve >> this, >> but then I need to mess with my msi and schedule RemoveExistingProducts >> near >> the end of the install to maintain settings in files like the >> web.config, as >> far as I know. Is this the recommended action? It is direction I'm leaning >> towards. >> >> The other option using the Bootstrapper at >> http://sourceforge.net/tracker/?group_id=105970&atid=654188 and >> modifying it >> with msistuff.exe setup.exe /o INSTALLUPD /d mymsi.msi /b mymsi.msi /v 200 >> /n "My Product". Using this requirements 1 and 5 aren't satisfied. >> >> Another option I have read is to use the GenerateBootstrapper task to >> launch >> a C# UI and check everything with that. But this sounds like a lot of >> unnecessary work and I don't know how to go about this. >> >> Also with either bootstrapper option I have tried the Visual Styles of my >> installer are gone. This is a minor issue except that the ComboBox drop >> down >> list do not show (you have to use the up and down keys to go through the >> options). Has anyone else experienced this? >> >> Thanks, >> >> -Matthew Rowan >> >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> Using Tomcat but need to do more? Need to support web services, security? >> Get stuff done quickly with pre-integrated technology to make your job >> easier. >> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users > -- Stefan Pavlik | [EMAIL PROTECTED] Whitestein Technologies | www.whitestein.com Panenska 28 | SK-81103 Bratislava | Slovak Republic Tel +421(2)5930-0735 | Fax +421(2)5443-5512 ------------------------------------------------------------------------- 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
