Eric Hybner wrote:
I'll submit an enhancement request for Heat. It seems like we could
add a switch (perhaps in file-mode only if it is too giving us much
rope for directories) that would override the registry location, run
an exe with the regserver switch, capture the diff, and provide the
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Hybner
Sent: Thursday, December 21, 2006 3:07 PM
To: Bob Arnson
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Extracting COM data from executable COM
servers(AppID) with heat.exe
As always, thank you for your help, Bob.
As always, thank you for your help, Bob.
I'll submit an enhancement request for Heat. It seems like we could add
a switch (perhaps in file-mode only if it is too giving us much rope for
directories) that would override the registry location, run an exe with
the regserver switch, capture the dif
Eric Hybner wrote:
Do y'all have any pointers for extracting COM data from executable COM
servers?
The technique Heat uses to detect self-reg data only works on in-proc
servers. I don't think there's a way for Heat to support out-of-proc
servers.
--
sig://boB
http://bobs.org
--
Do y'all have any pointers for extracting COM data from executable COM
servers? When I heat (-gg) BOB.exe (a legacy VB component not quite
ready to be retired) for example, I get something like this:
I get the HKCR\Interface\{6DD...} and HKCR\TypeLib\{6DD...} d
5 matches
Mail list logo