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.