That list matches the areas I remove, I'm afraid the only way to be sure
is to remove them then test on a clean machine - I recommend using a VM
for this, if you don't already, so you can keep rolling it back. Another
approach is too look at the output from a non-VB6 COM component and only
leave in the bits it has, if my memory serves me right you should only
need one or more progids that point at classids and the classid may
point at a typelib entry - somewhere in the mix there can also be an
appid entry.
I hope this helps.
Neil
From: Cheyne, Mark A - DNR [mailto:[EMAIL PROTECTED]
Sent: 13 June 2007 22:05
To: Neil Sleightholm; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Heat and vb6 dll?
I had a hunch about that, just a bit timid with the knife.
What do you think the definition of 'unnecessary' is?
If I were to guess, I'd hack out <class>, <typelib>, <registryvalue>
elements that refer to things not defined in my DLL itself. For example,
in my heat-generated *.wxs I see a <class> element for VBPropertyBag, a
<RegistryValue> for msvbvm60.dll, two <RegistryValue> elements for a
helpdir in system32, a <TypeLib> for VBA, and a <TypeLib> for Visual
Basic runtime objects and procedures.
Thanks, Mark
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Neil
Sleightholm
Sent: Wednesday, June 13, 2007 3:51 PM
To: Cheyne, Mark A - DNR; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat and vb6 dll?
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
