Need to include original DLL with Interop?

[Tom]

Hi,

I have developed a VB.NET app that is referencing and using an old ActiveX
component. When I add that reference to .NET, it of course generates an
interop file. My question is: If I include the interop file with the
application when deploying, do I need the original .dll object?

For example, say I am including an old ActiveX component called
OldActiveX.dll. .NET will generate an interop.OldActiveX.dll file. When I
get ready to deploy my application, can I just deploy the interop file? Or
do I have to deploy BOTH the interop file and the original OldActiveX.dll
file?

Tom

[Marina]

I believe the wrapper is just that - all it does is marshall the calls to
the real DLL. It is not a converted version of the DLL - it just relays the
calls to the real thing.

So yes, you do need the original DLL (and probably need to register it as
well).

"Tom" <to*@nospam.com> wrote in message
news:%2***************@TK2MSFTNGP11.phx.gbl...

Hi,

I have developed a VB.NET app that is referencing and using an old ActiveX
component. When I add that reference to .NET, it of course generates an
interop file. My question is: If I include the interop file with the
application when deploying, do I need the original .dll object?

For example, say I am including an old ActiveX component called
OldActiveX.dll. .NET will generate an interop.OldActiveX.dll file. When I
get ready to deploy my application, can I just deploy the interop file? Or
do I have to deploy BOTH the interop file and the original OldActiveX.dll
file?

Tom