Clemens just posts an answer he wrote to an email question regarding the very common question is Remoting dead?
Here is the answer he put:
Peter,
Nothing is “dead” until it doesn’t ship anymore and then subsequently becomes unsupported. The long-proclaimed-dead COM is very much alive and kicking and there’s even work being done underneath on MS RPC. Remoting is the technology used to communicate across AppDomains within the same process that’s baked into the .NET Framework. As such, it’s very much alive.
Does it have any great & bright future in terms of being a distributed systems technology for communicating across the network and will see any significant investments? No. Our strategic technology for building distributed systems is the Windows Communication Foundation.
Our guidance has been – for the last few years – that you use Web Services (ASM/WSE) by default for whenever you cross a network boundary and if you happen to need features from Enterprise Services or cannot use IIS as your application host, you use ES instead. If you need reliable, durable communication you use MSMQ. Remoting you’d typically only use in cases where you need a more or less convenient way get CLR typed data across a TCP socket – tightly-coupled, non-interoperable, limited security needs, limited scale.
If you choose Remoting, you should avoid client-activated objects, marshal-by-ref, delegates, events and direct access to fields and/or properties. All that will not only make a later migration easier, but is also a good recipe to avoid the most common distributed object system disaster scenarios.
Lastly, this is not so much a matter of opinion as one of reading and understanding what we’ve been saying for quite a while.
Clemens
I Highlighted the “important” stuff for you. Some see a path here???