The convention is that the Dll developer adds OLESelfRegister to the
resources. That's used as a clue for a lot of the tools out there.
I'm puzzled by the reference to a tlb file - did you try to loadlibrary on
it? That's not how tlb files are used. Also, you've noticed that
LoadLibrary requires that any dependent Dlls get loaded too, and if they
can't be found then the Dll won't load. There might be some LoadLibraryEx
flags that might help if all you want to do is see if there is a
DllRegisterServer, and not actually call it.

Signature
Phil Wilson
[MVP Windows Installer]
> Hi guys,
>
[quoted text clipped - 17 lines]
> Thanks,
> Martin
Martin Zugec - 10 Mar 2008 11:05 GMT
Hello Phil,
thanks for answer, using OLESelfRegister looks like better way to
handle it... Any idea how to detect if it is in file resources??? Any
help is really appreciated, specially any bit of code ;)
Thanks,
Martin