In article <[EMAIL PROTECTED]>,
Rob Mensching <[EMAIL PROTECTED]> writes:
> If anyone does figure it out, it'd be good to understand what is going on.
> I don't know VB (let alone VB6) and things work great for my C++/ATL based
> COM objects.
By the time its a COM object, VB6 or C++ it doesn't make any
difference.
I would run RegMon and FileMon while you hand register the COM object
on a system where its never been registered before. Then check to
make sure it isn't doing things inside its DllRegisterServer that its
not supposed to be doing (through filemon). Its only supposed to be
setting registry values that deal with COM registration, but sometimes
people get lazy and do all sorts of crazy stuff in there. I don't
know if VB6 lets you control that entry point or just does it for you
based on the kind of project you made. At any rate, all that's
happening when you register the COM object with Windows Installer is
that its handling those registry entries for you.
If you duplicate all of the registry entries, then it should work
fine.
The key is going to be running some sort of utility that can tell you
how that component is interacting with the system when its
DllRegisterServer entry point is called. Ultimately you could (ugh)
step through the assembly code as it executes to identify the missing
piece.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
