Re: IDispatch Interface

Tech-Archive recommends: Fix windows errors by optimizing your registry

"expvb" <nobody@xxxxxxx> wrote:
I don't have the same level of knowledge of the inner working of
COM as others in this thread, but TLB files are not DLL files. You
can create TLB's in many ways, and there are probably tools
out there that create TLB files out of COM files.

ActiveX DLLs, EXEs and OCXs contain Type Libraries. Use
OLEView to open a specific DLL, OCX or EXE (or other?).

You can then recompile the Type Library presented by OLEView
with a MIDL compiler.

Hope this helps.

--
Jim Carlock
Post replies to the group.


.

Relevant Pages

  • Re: IDispatch Interface
    ... It gets its information from the typelib. ... and there are probably tools out there that create TLB files out of COM ... Here are some useful links about creating type libraries: ... How To Make C DLL More Accessible to VB with a Type Library ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6 app interop with VB.NET dll
    ... assembly and re-deploy it to the VB 6 PC that I see these wierd ... Is re-deploying the dll and tlb files as easy as overwriting them? ...
    (microsoft.public.dotnet.framework.interop)
  • Re: COM tlb file
    ... Tlb files are not needed in C++, you can #import a DLL, OCX or Exe. ... In reality TLB files are embedded in the file resource, ... The TLB file contains the compiled IDL information, ...
    (microsoft.public.dotnet.languages.vc)
  • Cannot find assembly
    ... I have a DLL that I developed in .Net and marked to register for interop. ... The DLL relies on a second DLL that is also registered for interop. ... dll files and their tlb files are all in the same folder. ... executable file into the folder containing the dll and tlb files, ...
    (microsoft.public.dotnet.framework.interop)