> The UI part gathers the information from the user and the target system as > usual, then opens the MSI database of the target package, "patches" it with > new GUIDs, starts the main installation as msiexec /I > <list_of_public_properties> and silently closes itself. In such case every > time you install your product, from the system point of view it launches a > different MSI package each time.
> I'm not sure if it is the way to go for your case and if it's at all the > WiX-like approach. But when I was searching for the solution to this > problem, this is the best advice I managed to get. I have just thought the same, the use of setup bootstrapper that patches the MSI on the fly is, I think, a good solution. Similar as when preparing multilanguage support. As described here: http://www.tramontana.co.hu/wix/lesson9.php. You have to, in some how, modify/change update code so the Windows Installer will think it as a setup of other application and install the same application next to prevously installed. Best regards, Peter Jaworski ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
