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.
Please do not answer using the WCF Trace tool unless give explicit instructions on how to capture the actual message including headers and faults. This link does not work.
Also, do not answer IClientMessageInspector unless you know how to get it to include all headers (which it doesn’t) and capture responses that have fault elements that don’t parse.
With pre-wcf web services, you could write a SoapExtension that worked flawlessly.
write a custom message encoder. it has access to all headers. deoending on how generic you want your solution to be you may need to write it such that it gets in the ctor the real encoder.
just a few days ago I implemented a “Wrapper encoder” in this thread. that encoder changed the message. you don’t need to do this, you can just log it and pass it to the transport as I also did.