Tom Quarendon wrote: > It trying to harvest some COM registration information from a couple of > COM servers, one a DLL and one an EXE.
Heat (and Tallow before it) can't harvest registry information from out-of-proc COM servers -- the technique it uses works only for in-proc servers. > Since the > output for the DLL isn't a list of registry keys as I would expect would > be generated by the self registration harvester, I assume that the > Assembly Harvester is being used 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. > This is my first experience of trying to write COM components and get > them installed and it all seems desperately complicated. Maybe I'm > missing something. > 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. -- sig://boB http://bobs.org ------------------------------------------------------------------------- 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
