wtf are AxInterop and Interop dll's? :-)

[DraguVaso]

Hi,

I'm working alreaddy a lot of time with VS.NET 2003, and never payed a lto
of attention to the AxInterop and Interop dll's it creates.
Although this weekend I had a problem caused by them, and I began to aks
myself what they really do, what they stand for etc? What's the difference
with the 'old' kind of dll's? And how does it come that they can't/don't
need to be registered with regsvr32?

Any information would be welcome, like the problems and needs that they
demand...

Like this week I had a problem with such an Interop-dll that sudenly gave a
conflict, and when I recompiled the application was good. When copying the
new Interop-dll to the client's everythign seemed to work well, although
some things didn't work anymore. copying the according AxInterop-dll (and
replacing the 'old') did the truc. Those things seems strange to me: I don't
really understand why 2 the same versions (but compiled on another day) give
a problem, and why the seem to be 'together'?

Thanks,

Pieter

 

[Jared]

It is a runtime callable wrapper, they are created automatically when you
reference a COM object in your project. It doesn't need to be registered
because they are managed .dll's; you can create your own
Interop.Componentname.dll by using the tlbimp and tlbexp tools provided by
VS.
Read more about RCW's @

ms-help://MS.VSCC.2003/MS.MSDNQTR.2003FEB.1033/cpguide/html/cpconruntimecallablewrapper.htm

 

[Willy Denoyette [MVP]]

It is a runtime callable wrapper, they are created automatically when you
reference a COM object in your project. It doesn't need to be registered
because they are managed .dll's; you can create your own
Interop.Componentname.dll by using the tlbimp and tlbexp tools provided by
VS.
Read more about RCW's @

RCW and CCW are objects created by the CLR when managed code calls into
native COM or native COM calls into managed code. Interop assemblies are
managed assemblies containing COM's typelib info translated to metadata.

Willy.