In my experience I have found you need to remove the detritus that
Microsoft feels the need to include during the self registration of VB6
COM DLLs. So basically I use heat/tallow as a guide to save time, then
hack out all the unnecessary items.
Neil
From: Cheyne, Mark A - DNR [mailto:[EMAIL PROTECTED]
Sent: 12 June 2007 23:45
To: Neil Sleightholm; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
As Neil's reply is actually a solution to my other post:
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg09440.htm
l
I thought I'd restate _this_ problem, which remains unsolved.
The problem here is that I run heat.exe on a VB6 DLL that I authored, as
a way to generate a *.wxs file containing a <FRAGMENT> with all the COM
registration muck I need to install and register that DLL. The problem
is that the output *.wxs contains errors that prevent me from building.
See my enumeration of errors 1, 2, 3 at the bottom of this thread.
Any thoughts? These errors refer to a class and typelibs that are part
of VB6 itself, not my DLL, and yet heat.exe emits (erroneous,
incomplete?) metadata about them when I point it at my DLL.
Thanks, all - I'm almost there! Mark
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
