So I tried to move from Tallow to Heat because, well, when I use Tallow, I have to manually edit Tallow's output to delete short filenames so it works with WiX3...
Particularly challenging part of my projects is to generate WiX files for sample input/output. This sample input/output is on the order of magnitude of 1000's of files... So Heat proliferates the heck out of IMO unnecessary components, one component for each file. It should IMO be just two components (one per directory) but it ends up a few thousand...so-what, there's ComponentGroups, right? But when I put the ComponentRef into a Feature, then Candle/Light complain how Windows Installer only allows 1600 components per feature max, and on Win9x that number is only 800 (something). So now I'm back to manually editing output of Heat to sporadically add "Feature" tags in between components... 1) What am I missing? Is Heat not designed to reduce the task of including 3000 files to adding a <ComponentGroupRef> (or whatever) line to a "Feature" ? 2) Why does the Heat output have one (blank, and duplicated) DirectoryRef each time there is a component in the one directory? Wouldn't this degrade performance... 3) Is there a way to tell Heat that the path to the files is ..\Whatever, NOT a variable, NOT the silly string it uses by default? ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
