CODEWITHSUNDEEP
wixdcomheat
Tiger Galo
Tiger Galo

Reputation: 351

WiX Heat tool cannot harvest info from executables

Can anyone confirm that heat works only on DLLs, OCX, maybe some other files, but not on executable files?

The thing is, that I run heat on my COM components DLLs or OCXs (registered through regasm, regsvr32) and it harvests all data in the registry related to the file. However, I have DCOM servers that have lots of info related to themselves in the registry (self registered using /regserver) and the harvesting tool extracts just a minimal information about the file itself but nothing from registry related to the file, NOTHING. Like the resulted wxs file could be something like this:

<?xml version="1.0" encoding="utf-8"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi">
    <Fragment>
        <DirectoryRef Id="INSTALLFOLDER">
            <Component Id="ohserver.exe" Guid="{E8D87743-45B6-459E-A72F-22D9A0D5CE16}">
                <File Id="ohserver.exe" KeyPath="yes" Source="SourceDir\ohserver.exe" />
            </Component>
        </DirectoryRef>
    </Fragment>
</Wix>

As you see nothing from registry, CLSIDs, ProgIDs, RegistryValues, etc.

Upvotes: 0

Views: 327

Answers (1)

Bob Arnson
Bob Arnson

Reputation: 21896

That's correct. Heat does not support harvest self-reg data from .exe servers.

Upvotes: 2

Related Questions