Yes remoting is the .NET way.
But if you want to stick with COM,
You can expose a .NET component via a COM interface.
The COM client can then invoke the .NET component via CoCreateInstanceEx(),
specifying the remote server.
You need to explort the TLB on the client (caller) in order to make this
work, just as with normal COM.
Did you try this?
System.EnterpriseServices also supports hosting remote .NET components.
-D
"Saurabh Nandu" <sa*****@NOSPAM.mastercsharp.com> wrote in message
news:e8**************@TK2MSFTNGP09.phx.gbl...
Hi,
Yes, there is no concept of out-of process server in .NET. The closest
match would be to create a Remoting server and running it in a different
application domain.
Regards,
Akila