I'm working on a project which involves clients calling into server and server calling back to the clients. I use .Net Remoting to do that (setting TypeFilterLevel to Full and creating the client and server sink providers on both sides). It works great and fine within my intranet ...

i'm using custom sink channels to encrypt (among other things) my remoting
tcp channels, but i've noticed that for every call, even though its a client
activated object, it opens a new tcp connection and leaves it open until i
run out of available sockets at around 4000 ...

I have a case where the given assembly may or may not reside on same machine, so to make things scalable/uniform i thought of using remoting for local as well remote assemblies.
Has anybody benchmarked use of remoting on same machine instead of direct usage of assembly?
What are ...

I'm having an issue here that's driving me nuts! To resume things, I have a
vb.net desktop application (appA) that creates a new appDomain, and inside
that domain it loads another vb.net desktop application (appB). Both
applications have a UI.

I need an object to live as long as the application is running. I use a
remote factory to create the object which needs to live.
What is the best way to handle this? I've read many articles but I just
can't seem to get it figured out.

i have a requirement..
1. i have lot of BL objects hosted in IIS single call mode,
2. depends on the parameter given to the methods, or some time if there is
no parameter also.. we will go and read an xml file which is present in

i have a remoting host on my dev machine which works perfectly but when
brought onto server machine it starts but does not seem to accept any
connections.
I do a netstat -a and the port is listening and when i connect to the

I have been doing alot of reading about remoting, etc. but am still confused
and a little lost.
Problem: I have three applications that all use the same assembly (ie:
MyApp.dll). I want the assembly to be loaded only once (singleton?) and have

I´am working with remoting for a while now (with the help of Ingo
Rammer´s book)!
But now I am really stuck!
At the moment I have several Singlecall remoting object hosted within a

Is it possible to have 2 separate objects bind to 2 different channels from the client side? Given the following confg, how can one register one object to use one channel (versioned) and the another use the other (non-versioned)? RemotingConfiguration.Configure() will register ...

I have developed a small windows service that use .net remoting.
What this service is supposed to do is it has to ping my Remoting Server
Process on each timer tick and will write the response to a text file.
i have added a Timer Control in this Service and Set its properties to

I want to marshal object in an IIS hosted application. It works fine when
RemotingServices.Marshal is called in the original AppDomain. But when I
create new AppDomain and marshal there, the object cannot be accessed
remotely.

in .Net remoting, I can get the Remote Object Name, Type, MethodName,
Parameters. all in string format.
How can I construct a MethodCall?
Can I manage it using Object MethodCall? and How?

I have seen posts by many beginners asking how to use remoting with
GUIs.  In my own experience, I have instantiated the remote object
within the server's form object, made it available to clients using
RemotingServices.Marshal(), and attached event listeners to the object

I have a wellknown singleton remotable object within a Windows service
working.  I can use Activator.GetObject to get the object from another
process fine.
However, I would like to instantiate the single object from within the