reference to *.dll vs *.tlb

reference to .dll vs .tlb

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Achim Domma - 31 Mar 2006 16:34 GMT

Hi,

if I add a reference to a type library in a *.tlb file to my project, I
don't get a extra interop dll. If I add a reference to a *.dll
containing the type library and the com object, I get a interop dll.

Is there a way to compile all my code in one single dll, even when
referencing the COM dll? I want to have only a single dll for deployment.

regards,
Achim

Reply to this Message

Scott M. - 31 Mar 2006 18:05 GMT

No. One .dll can only contain compiled code from one architecture. .NET
assebmlies and COM components use 2 different architectures.

> Hi,
>
[quoted text clipped - 7 lines]
> regards,
> Achim

Reply to this Message

Achim Domma - 31 Mar 2006 21:21 GMT

> No. One .dll can only contain compiled code from one architecture. .NET
> assebmlies and COM components use 2 different architectures.

Yes, that's clear to me. But currently I have 3 dlls:

1. my main dll
2. some interop.xyz.dll
3. dll containing the COM component

3. is out of my control, but I want to have 1. and 2. in one single dll.

regards,
Achim

Reply to this Message

Scott M. - 31 Mar 2006 23:08 GMT

If you could find a way to de-compile the IntrerOp .dll and then put that
code in .dll #1, I suppose you could, but I don't think you can do this.

>> No. One .dll can only contain compiled code from one architecture. .NET
>> assebmlies and COM components use 2 different architectures.
[quoted text clipped - 9 lines]
> regards,
> Achim

Reply to this Message

reference to *.dll vs *.tlb

Free Magazines

reference to .dll vs .tlb