If the base class doesn't derive from MarshalByRefObject then it's never going to be directly remoteable. If that's the case you'll have to write a remoting facade for it.
But you probably want to do that anyway, even if the base class does derive from MarshalByRefObject. It's almost invariable a mistake to take existing types and try to 'remote' them. Remoting boundaries are completely different kinds of things from normal class APIs. Error characteristics are different, as is latency. Programs that don't draw very clear distinctions around these boundaries tend not to work very well. So your best bet is almost certainly going to be to write a class whose sole job is to present a remoteable API to the outside world, and then have that make calls onto the underlying implementation. -- Ian Griffiths - DevelopMentor (RSS: http://www.interact-sw.co.uk/iangblog/rss2.0 ) > -----Original Message----- > From: Bill Bassler > > What are the high-level steps/requirements to remote an object that > already > inherits from another class? =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
