After receiving emails from people on this subject asking about our process, I will reply to all publicly here.
Unfortunatly my employer 'owns' the code, getting OS in the door is hard enough, getting it out is not an option I am afraid. However for those interested the general methodology used is as follows. Each file has an XML file which describes it, how it gets installed and any required params which cannot be auto harvested. It also lists what products this file gets used by ( we have a lot of code sharing among products). This file is then read and generates wix source files for each product using transforms and xpath. This pass also tell the products what components they have. The component files are then built, tranforms are done to generate the features using the information from pass 1 and then the final generation of msms and then msis. This process currently manages our msi generation for 20+ installation products from 240ish components built from source and a few hundred ancillary files. It removes most of the tedium and mistakes made, but is still fully extensible by careful use of include files. It's not quite the nirvana of fully automated code generation but it does remove the tedium and potential mistakes from changing one component which is used in all products. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
