I've been using WiX 3.0.2925 to install some of our COM DLLs
(created by Visual Basic 6.0 SP6).
With WiX 3.0.2925 when I use:
"heat file MyLibrary.dll -out MyLibrary.wxs"
I will often get a mixture of <TypeLib> entries (which is what I
want) and a mixture of <RegistryValue> entries (which seem to be instead
of other <TypeLib> entries).
This makes it very difficult to edit a wxs file when interfaces
have changed etc.
Is there any way to force heat to produce only the <TypeLib>
entries?
David,
Not that I know of.
I strip out everything apart from the TypeLib element inside the File
element for my DLL.
Most of the rest outside the File element seems to be RegistryValue
elements and the other TypeLibs to do with the VB runtime. The VB
runtime gets installed elsewhere and it seems to me that installing
those registry entries violates the component rules. More worringly they
contain hard-coded strings such as "C:\WINDOWS\system32\MSVBVM60.DLL",
which is clearly wrong.
This approach seems to work for me, but I would be interested to know
whether it works for other people.
Cheers,
John
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
