[EMAIL PROTECTED] wrote: > It's a slightly unusual option, but if I was in your shoes I might > consider supplying the application packaged as a wixlib (containing the > main application installation), together with a utility which allows the > reseller to select their "template" folder. After verifying that the
You are making it too complicated. Wix is a great toolkit as it allows the generation of the installer files directly from the command line. To me at least, the obvious solution to create *many* semi-customized MSI files and to be sane is automation. For example, create a small web application where resellers can add their own logos, text options, etc. The web application then stores the stuff in some database. You then write a script that takes the data from the database and creates a file that will be included in the main wix file. Then you run make. Put the resulting MSI in the database (or reference in database) allowing each reseller to get their customized MSI directly from you. If they need changes like logo, they can just change it via the web app. So, you still end up with 40 MSI builds, but it becomes automated. I was going to write this is suitable for small and medium sized MSI files, but I think it would work with DVD sized ones as well. Disk space is cheap. CPU power is cheap. - Adam -- Mail Etiquette ============== * Quote properly or not at all. Top posters, this applies to you! * When replying to posts on mailing lists, only address the mailing list unless poster explicitly requested you include them in CC ------------------------------------------------------------------------- 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
