You can add rejectRemoteRequests="true" on the server side tcp or http channels. With this set remoting will only allow connections from the loopback address and thus will reject cross machine calls. This is equivalent to setting bindTo="127.0.0.1" or...

Most remoting users have seen one of the following exception messages during deserialization: Because of security restrictions, the type XXX cannot be accessed Type XXX and the types derived from it (such as {YYY}) are not permitted to be deserialized...

My post from last week talked about OneWay messages in remoting. I should have clarified that the async and one way behaviour occurs only when invoking a method marked with [OneWay] on a remoting proxy. Invoking the same method on a regular object will...

There is a common misconception that using remoting leads to memory leaks. The fact is that the problems mostly lie in the server design more that in the use of remoting. There are two issues which often lead to server side leaks: 1. It could be related...

RemotingServices.Marshal allows you to publish an existing instance remotely. Both for server activated (wellknown) and client activated objects remoting controls when the object is instantiated and initialized. Using Marshal allows you to initialize...

Remoting provides a way for fire-and-forget OneWay messages from client to the server. Just adding a [OneWay] attribute to a method of your remoted type would make the method invokation oneway. Something like: public class Remote : MarshalByRefObject...

One issue with NLB and remoting is the fact that remoting clients cache sockets connections for performance reasons. The side effect of this is that in the NLB case subsequent calls from the same client go to the same server introducing server affinity...

Events and Delegates are supported in remoting. So x-appdomain and x-process delegates and eventing does work. The guidance is to not use them in cases where channels could be unreliable. In case where channels are unreliable (mostly the network in x...

Exceptions are serializable (ISerializable too). Exceptions are serialized from the server back the client. Thus if you see a client side exception with the following stack trace, there is a good chance you are actually seeing an exception which was thrown...

CallContext allows you to flow information with a "logical" call. With logical we mean the call doesnt necessarily have to happen on the same thread. Following constitute logical calls: 1. remoting calls made x-appdomain and x-process 2. Async delegate...

When hosted in IIS / Asp.Net and using the binary formatter you might run into an exception saying "BinaryFormatter Version incompatibility. Expected Version 1.0. Received Version 1950887522.2017816692". The issue here is that under various error conditions...

Remoting in v2.0 of the framework is introducing a new IPC Channel meant for x-proc communication on the same machine. It is based on named pipes and works on win2k based platforms (win2k, winxp, win2k3). It will provide better performance characteristics...