> Heat converts the registry information it gathers into strongly-typed > WiX authoring. Take a look at > src\ext\UtilExtension\wixext\UtilFinalizeHarvesterMutator.cs for where > that particular magic happens.
I found that bit shortly after I posted. Thanks though. > If they're components you're developing, you already have all the > information that goes into the installation. It's probably easier to > write and test that once than it is to harvest from the binaries. I was hoping for an automatic way of doing it even if I only do it once. I've got quite a few interfaces and classes, and each one has a number of registry entries associated with it. Seems astonishing to me that the answer to this problem is "write the wix file manually". There is a technique on The Code Project for capturing registry entries written by out of process EXEs, but I guess that wouldn't be suitable for use from C# (involves starting the process up "suspended", and then injecting code into it to load a DLL which then does the work of calling the registry hive redirection API so that the registry keys can be captured). Other methods seem to be to interpret the .rgs files that are stored as resources in the exe (this is an ATL based COM component), but tallow doesn't read .rgs files, only .reg files. Maybe that's another form of harvester that could be available. I'm happy to the process of authoring the Wix file once, but would rather do it with a tool to save any silly mistakes, and probably a lot of time. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
