>>
> >>>
> >>> Am 26.05.2012 16:10, schrieb Brian C:
> >>>>
> >>>> For us, we compared the heat extraction with the .reg results from
> >> using RegSpy for our 64 bit dlls. Everything was the same except the
> >> source
> using RegSpy for our 64 bit dlls. Everything was the same except the
>> source path, so the script just copies the .wxs generated by heat and
>> replaces the source path with the 64 bit location.
>>>>
>>>> Brian
>>>>
>>>>
ies the .wxs generated by heat and
> replaces the source path with the 64 bit location.
> >>
> >> Brian
> >>
> >>
> >> ____________
> >>From: Brian C
> >> To: General discussion for Windows Installer XML toolse
;
>>From: Brian C
>> To: General discussion for Windows Installer XML
>> toolset.
>> Sent: Friday, May 25, 2012 11:46 PM
>> Subject: Re: [WiX-users] harvesting COM information using he
> path with the 64 bit location.
>
> Brian
>
>
>
> From: Brian C
> To: General discussion for Windows Installer XML
> toolset.
> Sent: Friday, May 25, 2012 11:46 PM
> Subject: Re: [WiX-users] harvesting COM information using heat.e
From: Brian C
To: General discussion for Windows Installer XML toolset.
Sent: Friday, May 25, 2012 11:46 PM
Subject: Re: [WiX-users] harvesting COM information using heat.exe results in
HEAT5150
Heat does not extract for 64-bit dlls. We have had to write a script to
"convert
[WiX-users] harvesting COM information using heat.exe results in
HEAT5150
Hi there,
I try to extract the self-register information for a COM file written
with VB6 a long time ago.
If I use regsvr32 to register the file manually on Win7 64-bit it works
fine. But when I try to extract the i
Hi there,
I try to extract the self-register information for a COM file written
with VB6 a long time ago.
If I use regsvr32 to register the file manually on Win7 64-bit it works
fine. But when I try to extract the information using heat with the
following command line, just the file tag is gen
8 matches
Mail list logo
