Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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.
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”.