Author: Karol Kolenda | Posted on: 6/7/2008 8:04:10 AM | Views : 495

Hi guys, 
I've just installed beta 2 and checked an error propagation from WCF service to Silverlight. Unfortunatelly, I haven't noticed any differences in this area as Silverlight still reports 404.
Questions:
1. Does beta2 contain some improvements re: WCF faults and I just have to set some magical flag  somewhere in the code/web.config?
2. If the answer for the first question is still "no", can someone share with me her/his workarounds in this area? 
I've already found two solutions at Silverlight.net forum:
a) adding an error "out" parameter at the end of every method contract (but you have to change your interfaces and everything starts to look like good old flat DLLs :-)
b)  trapping and rewritting messages in global.asax. This looks more promising but it's a huge hack and I'm not sure if I want to follow that advice.
Any other ideas? 
Thanks
...

Go to the complete details ...