Prescriptive advice for minimally invasive conversion from Remoting to WCF
Are the tips in this highly cited MSDN article still considered sound for converting a .NET Remoting application to WCF?
I notice that the article is referring to the deprecated ServiceBehavior ReturnUnknownExceptionsAsFaults attribute, so I doubt if people have found other discrepancies or other approaches more appropriate for introducing WCF into an existing application in the meantime.
+2
neontapir
source
to share
1 answer
Considering that Integration with .NET Remoting refers to it (" From .NET Remoting to Windows Communication Foundation (WCF) "), I think the answer should be yes.
0
John saunders
source
to share