> 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'
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
It trying to harvest some COM registration information from a couple of
COM servers, one a DLL and one an EXE. I'm trying to use heat, and it
seems to work for the DLL but not completely for the EXE.
For the DLL I get a TypeLib element containing an AppId containing Class
elements, and the TypeL
3 matches
Mail list logo
