> Bear in mind that heat.exe isn't a substitute for actual setup > development. It's a tool to make doing things (initially) easier > especially for people migrating from things like InstallShield where > there's a lot of stuff hidden from/done for you in the background.
I'm not trying to be critical of anything, just wanting to understand something that appears counterintuitive. What constitutes "setup development"? What I read leads me to believe it means "100% manual WiX code production and maintenance". (I could be wrong here.) . . . My situation... My client's development team of dozen or so produces scores of DLLs, perhaps 80 or more. They expect the install build process scoop up the assembly DLLs produced by the build system, and the resulting MSI to drop the files in the correct directory. (The executables are fixed in WiX, the assemblies are not.) As far as I can tell (I may be wrong here) — unless one uses heat or some other method of code generation, this is impossible. WiX requires manual human intervention whenever the list of assemblies changes (which is frequent during active new development). Is this correct? If so, I'm struggling to understand how this is a Good Thing. It appears that that is having a human do what a computer is better suited to. If the list of DLLs is not exact, the automated testing system fails with a variety of symptoms, some a little cryptic. Again, my apologies if I'm way off in left field here. ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
