No, that's not correct at all. Programmers need to get away from exceptions
in WCF and they should avoid includeExceptionDetailInFaults like the plague,
because often enough, the code stays in all the way to production. Learn to
use fault contracts. Period.
--
Regards,
Alvin Bruney [MVP ASP.NET]
[Shameless Author plug]
Download OWC Black Book, 2nd Edition
Exclusively on
www.lulu.com/owc $15.00
Need a free copy of VSTS 2008 w/ MSDN Premium?
http://msmvps.com/blogs/alvin/Default.aspx
-------------------------------------------------------
"Jeff Winn" <jw***@nospam.comwrote in message
news:30**********************************@microsof t.com...
Hello!
Full duplex doesn't have anything to do with it, you need to add the
serviceDebug behavior to your service and set
includeExceptionDetailInFaults equal to true. Just be warned that
including exception information could cause a security risk depending on
your scenario. That will allow you to see the exception information that
occurred at the service. As for bubbling the information up to the UI, we
can't help you with that. It depends entirely on your application and how
you consume the services.
Here's a link explaining the setting:
http://msdn.microsoft.com/en-us/library/ms788993.aspx
Good luck!
"AAAAA" <ce*****@hotmail.comwrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...
>Hi Guys!!
I have a question,
I working with the WCF service in the BL
what rise the errors to the UI?
WCF should be Full duplex?
Thanks
Cesar