Groups | Blog | Home
all groups > dotnet remoting > september 2004 >

dotnet remoting : call remoting object from vba


Ken Kolda
9/7/2004 2:02:29 PM
Without knowing the specifics of what you're doing, the problem sounds like
you're trying to cast an object to an interface it doesn't implement. Very
likely, you have an assembly with an interface of the same name that you're
trying to cast your object to, but the interface it implements is defined in
a different assembly than the one you're using. This can often be an issue
with COM objects if you're not using a primary interop assembly (PIA).

Ken


[quoted text, click to view]

md
9/7/2004 10:00:26 PM
Hello

I've created a C# outlook addin that will get an object from the server
using dotnet remoting. The addin is marked as Register for Com interop. When
i try to cast the returned object into the a specific class, i get
"specified cast is invalid". The specific class is implemented in a
(separate) referenced assembly (located in the same directory as the addin
assembly on the client)... What can be wrong?

It does work from a native .NET client.

Thanks

Marco

mdissel NO[at]SPAM home.nl
9/8/2004 1:37:24 AM
[quoted text, click to view]

If i install the referenced assembly on the client in the GAC it's
working. It is necessary to install all referenced assemblies in the
GAC when using remoting from a COM client?

When i debug the outlook process, i can see that my referenced
assemblies are loaded (using the directory where the COM addin is
located)..

Thanks for your help!!

AddThis Social Bookmark Button