I'm aware of heat.exe and we have used to to seed our component.wxs files for our various wixlibs, but how do you deal with features like websites and help systems which often have dozens of files added at any time during development cycles? Re-running heat can work, sort of, it will change the component guids, but leaves the component Ids of existing components alone. Not sure how it deals with removed components.
I stumbled across this 3rd party tool called Paraffin that appears to solve this issue, but have not attempted to put it to use in our build environment. What have others used to deal with features that often have an ever growing (and sometimes shrinking) list of components? -- Tony ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
