MBR IT/.NET 247 : Passing VB6 object to remote object fails on microsoft.public.dotnet.framework.remoting

Passing VB6 object to remote object fails

Messages

Related Types

This message was discovered on microsoft.public.dotnet.framework.remoting.
Responses highlighted in red are from those people who are likely to be able to contribute good, authoratitive information to this discussion. They include Microsoft employees, MVP's and others who IMHO contribute well to these kinds of discussions.

Post a new message to this list...

JSB (VIP)

I understand that an object passed to a remote object must either derive from
MarshalByRefObject or be Serializable...and a VB6 object doesn't satisfy this
criteria.

I'm wondering if there are other approachs that would allow me to pass the
VB6 object to the remote object, for example: custom marshaling, interop
marshalling, subclassing Formatter class, etc.

or do I have to abandon Remoting until I convert the VB6 code to VB.NET or C#?

Thanks,
Jim

Reply to this message...

Ken Kolda

The only way I know of to do this is to create a MarshalByRefObject wrapper
class that holds your VB6 object and forwards method calls to it. Then just
remote that class.

Ken

"JSB" <Click here to reveal e-mail address> wrote in message
news:Click here to reveal e-mail address...
> I understand that an object passed to a remote object must either derive
from
> MarshalByRefObject or be Serializable...and a VB6 object doesn't satisfy
this
[Original message clipped]

Reply to this message...

System.MarshalByRefObject

MBR BootFX
Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

	Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd.
	Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com