Wilson, Phil wrote:
Well the issue is basically that registration of VB6 Dlls requires the
VB6 runtime to be installed on the system. That means you need the VB6
runtime on your dev machine where you're running Heat. Heat is
calling DllRegisterServer, which is calling into the VB6 runtime.
That much seems obvious, so if you already have the VB6 runtime on the
dev system then something else is going on (a possibility might be
that Heat is confused by seeing registration entries that have a
server other than your Dll).
The problem is that some DLLs unnecessarily rewrite their (or
parent/dependent DLLs') COM registration information. Heat just records
what the DLLs' self-reg code actually did, so it can't differentiate
between "good" self-reg and "bad" self-reg.
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
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
