I have heard from quite a few folks running into an issue where the IpcServerChannel would throw trying to initialize after a restart. IpcServerChannel by default creates pipes in exclusive mode (no other process can listen on the same pipe name)....

In most cases it is not quite obvious, but in scenarios where a client receives callbacks, or subscribes to events on the server, you need to make sure that the lease on the client object doesnt expire -- registering a sponsor for the client object is...

The Microsoft Operations Manager team has a number of development openings.If you are interested in working on cutting edge technology in enterprise monitoring and management space, this is your chance. Microsoft Operations Manager (MOM 2005) is already...

Now that .net Framework 2.0 is released -- a list of new features in remoting is in order. Following is a list of new features added to remoting: 1. IPCChannel: A new channel based on named pipes form x-process (same machine) communication. Its more...

This has been a frequently asked question about whether there is timeout support on remoting tcp channel. In 2.0 we have added support for timeouts. Unfortunately the support is missing in beta2 -- but should be available when 2.0 is released. The configuration...

After working on remoting for about five years (almost seven on the .net framework) I am changing focus and work in application development space. Thus I have now moved to the Microsoft Operations Manager team. I hope to continue to blog about remoting...

This has been a common ask to add some authorization support on remoting channels. During Beta1 remoting added support for authentication and encryption on the TCP channel. In Beta2 there is a new feature which lets you authorize connections based on...

There are config setting changes for Tcp channel authentication in .net framework 2.0 Beta2. Here is a sample server configuration, Note that secure="true" gives a setting of TokenImpersonationLevel.Identify and ProtectionLevel.EncryptAndSign: <configuration>...

Remoting does support stateful connections. You could use singleton or client activated objects to keep object state. This object state is not persisted however. If the server appdomain is unloaded all remoting state will be lost. Not only will the state...

RemotingServices.Disconnect is probably one of the confusing APIs in remoting. It doesnt correspond to RemotingServices.Connect, but rather to RemotingServices.Marshal. Disconnect is a server side API to disconnect objects which are currently published...

Thanks to all those who responded to Call for remoting apps.. . We will evaluate what remoting applications best fit our criteria and will contact you individually. Thanks again for helping in the remoting compatibility effort.

The .net remoting team is looking for customers to help us with compatibility. If you have existing standalone remoting apps based on v1.0 and v1.1 of the framework and are willing to help us ensure remoting compatibility with future versions of the framework...

Cloning MarshalByRefObjects can lead to some unexpected behaviour. When a MBR object is marshalled, it gets an unique identity which contains a unique URI to identify this object in the appdomain. When an external call is made to this object it is identified...

If you set machineName="foo.com" in the server side remoting config (to avoid using ip addresses) and probably need to deploy the same config on multiple servers use machineName="$hostName" and remoting will substitute this with the current host dns qualified...

A CLR type instance can be activated remotely in the following ways: 1. Through Config: This is probably the most common way. Use the client tag under system.runtime.remoting to register a type to go remote: <configuration> <system.runtime.remoting>...

This is probably not a very wellknown fact, but static methods and fields accessed via a remoting proxy, are actually executed locally on the client side. So even though a type is configured to go remote static accesses/invokations dont go remote. If...

Infact they could. The contract for a remoting singleton wellknown object is that "a" object would always be available on the remoting wellknown endpoint. It doesnt mean the same single instance is always available. Singletons also follow the same leasing...

Each remoting channel has a priority associated with it. If there are multiple channels registered in the same appdomain and a MarshalByRefObject is marshalled out, all available channel data will flow with the ObjRef. The order is which this channel...

Got an interesting question about how to deserialize delegates serialized with an older version of an assembly. While deserializing, if the older version isnt available the engine might throw a TypeLoadException. The Serialization binder doesnt help in...

A remoting client need not register a channel (if its http or tcp) when making a remote call. The remoting infrastructure will load an appropriate channel after looking at the scheme of the URL (tcp:// or http://). Though being explicit in code is goodness...

As is common knowledge remoting needs server assemblies on the client for remote communication. In many cases sharing server implementation with the clients is undesirable. Interfaces can be used to acheive this isolation. An assembly which contains only...

There are a couple of reasons why appdomain unloads can fail. One common failure is when all threads inside the appdomain cannot be unwound. This mostly happens when there are threads running unmanaged code. In a remoting case its possible a thread that...

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...