I'm in a similar situation with close to 30,000 files to deploy of which perhaps 50 - 100 are DLL's, EXE, OCX etc.
I've ended up grouping files together in a component, (with the exception of DLL's etc) sometimes up to 5,000 or 6,000 in one component. I also forced a version number for each file to ensure that if I had to perform an upgrade the file would be overwritten REGARDLESS if it had changed forcing integrity of the application. I've also disabled the repair option from ARP, but allow Repair from 'Change' and modified the ReinstallMode to anus. In my situation these deployed files are not updated by the application and should not be modified by the customer. If they have been modified by the customer I need the repair to restore the install back to deployment status. I would like to know the 'optimal' amount of files that should be contained in 1 component. As much as I'd love to give each file a unique component, filling the registry with 30,000 GUIDS just seems crazy. Neil ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
