Hello, This probably isn't a Wix-specific question, but please excuse me for asking here - I'm after a Wix-based solution.
I have to make the installer for a product that is sold on a module-by-module basis. The number of the modules is not known beforehand. A module ships on its own disk, which holds the same application core, and some extra stuff for the specific module. And the hard part: the desired (and natural) behaviour would be to show a single application installed, and present a single uninstaller (which OC would need to be merged somehow on the user's machine). Following the Wix tutorial I managed to make the installer for each disk, reuse the shared core components, target the same directory. It installs nicely, the core is removed after the last uninstall, etc. But the only way I could get things this far is to use different product/package codes, which seems to imply different entries in the "add/remove progs" list. There is no clear ordering between the modules, so making them as upgrades doesn't seem viable. And merge modules, AFAIK, can only be merged during compilation, on the developer machine. This is similar to "plugin" installations where the plugin later needs to be uninstalled together with the main product. Is there a good solution for these cases? Thanks, Jozsef ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
