COM interop q

  • Thread starter Thread starter Frank Rizzo
  • Start date Start date
F

Frank Rizzo

I am using a .net library from VB6.
So I do
regasm mylib.dll /tlb:mylib.tlb
to make it available to COM clients. As I understand, the command
actually generates a new .TLB file everytime you run the command.

So when I do REGASM, what actually gets registered: the DLL or the TLB?

In addition, when I deploy my VB6 app, I would copy mylib.dll and
mylib.tlb to the target PC. Would I need to run the REGASM command
again or can I simply register the existing .TLB file? If I can just
register the .TLB file, how can I do so? REGSVR32 does not seem to work
with the .TLB file.

Thanks
Frank
 
Frank,
So when I do REGASM, what actually gets registered: the DLL or the TLB?
Both


Would I need to run the REGASM command
again or can I simply register the existing .TLB file?
Click to expand...

Yes you need to run Regasm on the target machine, or have a setup
package that handles the registration.



Mattias
 
Mattias said:
Frank,


Yes you need to run Regasm on the target machine, or have a setup
package that handles the registration.
Click to expand...

So, are you saying that I don't actually need to distribute the .TLB
file since I have to run RegAsm on the target machine anyway (which will
recreate the .tlb file)?

Thanks
Frank
 
Frank,
So, are you saying that I don't actually need to distribute the .TLB
file since I have to run RegAsm on the target machine anyway (which will
recreate the .tlb file)?
Click to expand...

No, you don't necessarily have to distribute the TLB.



Mattias
 
Back
Top