I am trying to work through some automation scenarios regarding heat and some file-dependent Components. Here is the scenario... I have a product that consists of a set of .exes and dlls. I would like to use heat.exe to automatically generate these deliverables for me at build time. It does this well, but there are a few issues that I need to overcome.
One of the .exes needs to be installed as a service. Since the service .exe is always the same, I was wondering if there was a clever way to have a static .wxs define the <ServiceInstall> element for this .exe? For instance, can I simple create a Component with the <File> element without actually installing the .exe, but rather just reference the name of the .exe and path via <Directory> constructs? Similarly, I would like to do the same for a .dll that needs to be installed into the GAC. Have the actual .dll be harvested via heat, but have static additional configuration to the <File> element reside outside of the dynamically generated .wxs that heat creates. Thank you. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
