Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I see this answer: Custom WCF service - includeExceptionDetailInFaults but when I attempt to do that it complains that the "Name" attribute of the "behavior" element is null.

share|improve this question
add comment

1 Answer 1

Why you need to transfer exceptions details, just to debug? Then just enable wcf tracing in web config and get exceptions in trace viewer.

Look at this thread to know how to enable WCF tracing.

share|improve this answer
    
If I enable exception details in the result then I do not have to log in to the server. –  Chloraphil Aug 5 '13 at 13:20
    
Yes, but It looks like you need such behavior only for debug purposes. Why end user has to watch your exceptions? My personal set of tools for debugging services consist of: Fiddler, ULC loggin inside service, WCF logging enabled if needed. It is enough to debug and no problems with service config and multiple IIS bindings. –  Anton Khritonenkov Aug 6 '13 at 4:14
    
This is a development server and is not accessed outside of the development team. –  Chloraphil Aug 6 '13 at 13:15
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.