Sajo Jacob wrote:
Thanks! that explains the exe's but how about the dlls with this issue?
Hard to say without more detail. What's missing/wrong with what Heat
generates?
--
sig://boB
http://joyofsetup.com/
-
This SF.net
Sajo Jacob wrote:
>
> Thanks! that explains the exe's but how about the dlls with this issue?
>
64-bit DLLs? I don't know how heat.exe even manages to load and call
DllRegisterServer on 64-bit DLLs (it's a 32-bit .exe in the WiX download),
but it definitely doesn't produce what you'd expect. Ho
Thanks! that explains the exe's but how about the dlls with this issue?
Jacob
On 10/31/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
>
> Sajo Jacob wrote:
> > I ran heat against a set of self-registration dlls and exe's, I
> > compared the WXS generated by darking an MSI which contained the same
> >
Sajo Jacob wrote:
> I ran heat against a set of self-registration dlls and exe's, I
> compared the WXS generated by darking an MSI which contained the same
> dlls and spotted that although heat did create all the components but
> didn't generate the registry tags and class ids for some of the
>
I ran heat against a set of self-registration dlls and exe's, I compared the
WXS generated by darking an MSI which contained the same dlls and spotted
that although heat did create all the components but didn't generate the
registry tags and class ids for some of the components. Is this a known
iss
5 matches
Mail list logo
