views:

66

answers:

1

Is the advice given in this oft-cited MSDN article still considered sound for converting a .NET Remoting application to WCF?

I notice that the article references the deprecated ServiceBehavior attribute ReturnUnknownExceptionsAsFaults, so I question whether people have found other discrepancies or other approaches better suited to introducing WCF into an existing application in the meantime.

A: 

Considering that Integration with .NET Remoting links back to it ("From .NET Remoting to the Windows Communication Foundation (WCF)"), I guess the answer has to be "yes".

John Saunders
Thanks. I wanted to get a sanity check before I went down the rabbit hole.
neontapir