OK -- thanx. I thought for a second I had totally misunderstood how Windows Installer works.
I've dug out the MSI created by the original IS installer (it was actually an exe installer, but IS12 seems to be MSI-based anyway, with exe installers just being boostrap wrappers around an underlying MSI install). Decompiled it with dark, and I have most of the information I need now. It's not a straight switch-over -- IS provides scripting custom actions via it's own engine, as well as custom extensions to the MSI table, so I'll need to add a few things to my C++ helper dll, but this should be straightforward. This will actually be an extremely minor upgrade -- the major change is really the installer itself. In theory I could probably do a patch for the actual upgrade if I can make the existing exe installer do a proper administrative install. We're in beta, atm, though -- so I may not bother. Thanx for your help -- m Rob Mensching wrote: > Sorry, caught the end of this thread. > > 1. You need to maintain Component/@Guids according to the Component Rules. > It doesn't matter what tool you use to create the MSI. Once you ship, you > must maintain the GUIDs appropriately. > > 2. ProductCodes and UpgradeCodes need to be updated following the Windows > Installer rules for upgrades. Major upgrade? Change the ProductCode... etc. > > 3. Dark.exe can help get all of your authoring and it will preserve all the > GUIDs for you. Technically speaking, you should be able to switch at any > time and rebuild a functionally identical MSI file (although it may be a > little smaller since WiX tries very hard to only add the things you need). > > -----Original Message----- > From: Michael Owings [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 30, 2008 18:01 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Moving from InstallShield 12 to wix > > I'm currently in the process of moving from an InstallShield 12 (which I > loathe) project over to wix. I'd ideally like to be able to update the > next version of this project via wix. > > I'm wondering if I use the the same product and component IDs if I'd be > in good shape as far as an upgrading goes. Any gotchas I should be aware of? > > Thanx in advance -- m > -- > Teleoperate a roving mobile robot from the web: > http://www.swampgas.com/robotics/rover.html > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- Teleoperate a roving mobile robot from the web: http://www.swampgas.com/robotics/rover.html ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
