Automatic account creation is now enabled. Captcha authentication required for account creation and editing unless you are trusted here.
Heat
From WiX Wiki at MindCapers
Heat harvests the files in a folder and emits a WXS file. This is very handy for knocking up a first draft of a setup project:
heat.exe dir ''<input folder>'' -out ''<output file>'' -template:product
In addition to the code normally generated, the product template wraps the output in a Product element. It also sets up your root directories under TARGETDIR and produces a default feature containing references to the generated components. All you need to do is fill in the blanks, replacing placeholders like "PUT-PRODUCT-NAME-HERE" with appropriate values.
However, heat is considerably less useful after initial project setup, because there is no way to preserve component GUIDs when repeating the process to acquire new files.
Blog Entries
Help
You can use "heat.exe /?" for more information, however the command-line help is woefully incomplete. It makes no mention of switches like-gg(generate GUIDs) or
-sfrag(single fragment) and there are no doubt many more such hidden gems.
To extract information about a dll into a MyDllFrag.wxs you would use:
heat.exe file MyDll.DLL -out MyDllFrag.wxs
