Stas Klyachkovsky wrote: > > Could somebody share his/her experience w/ such conversion? >
Provided you're starting from an InstallShield MSI project, it's actually fairly straight-forward to do - should take you about a week to port a mid-complexity (I know, what sort of definition is that :-) setup. Some thoughts: * InstallScript needs to be ported to C++-or-similar custom actions (CAs). Better off if you have no InstallScript in the first place, but provided the InstallScript is non-GUI, this is perfectly doable. * Any existing InstallScript-controlled GUI will need to be redesigned. This will be a fun task for non-trivial GUIs, and, unless you have the time/inclination to do it, IMO it's a good reason to *not* port an IS installer to WiX. One option is to write the installer-wizard GUI separately from the installer itself. * Automated component-info extraction is harder to do in WiX (I'm thinking COM object & directory harvesting here), although more flexible (i.e. *you* get to write some of the .wxs-creation code). * WiX's pre-processor means your single-source project can build both 32-bit and 64-bit installers, woohoo! cheers, Karim -- View this message in context: http://www.nabble.com/Moving-existing-MSI-based-setup-to-WiX-roadmap-tp15569833p15596175.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- 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
