WCF Feb CTP message logging
I was trying to get messages logged using Indigo's built in tracing/logging feature. As described here, I faithfully followed all the steps (although they seem to be intended for Jan CTP and the steps don't quite match). Lots of info about Indigo's inner workings gets in the traces etc, but no sign of SOAP envelopes!
As it finally turned out, there is a bug in Feb CTP where the wrong source name gets in the configuration when the svcConfigEditor tool is used. Fortunately this is documented in the Windows SDK Readme as follows:
6.4.5 WCF Message Logging Inoperative When Activated with the svcConfigEditor.exe Tool
When activating Message Logging using the Diagnostics screen in the WCF svcConfigEditor.exe tool, the tool adds the wrong source name— “System.ServiceModel.Channels.MessageLogging” instead of the correct source of “System.ServiceModel.MessageLogging.” As a result, message logging does not work, but no exception is thrown. This is a known issue that will be addressed in a future release.
Workaround
• Use the tool to open the Configuration you created.
• In the tool’s Configuration pane, click the “Diagnostics” item.
• In the Diagnostics pane, check the “Default message logging” checkbox.
• In the Configuration pane, expand the “Sources” item.
• Click on the source name.
• Rename the “System.ServiceModel.Channels.MessageLogging” source to “System.ServiceModel.MessageLogging” and save the file.
In addition, this version of the svcConfigEditor.exe tool does not, by default, activate either service-level or transport-level message logging. One of these two options must be enabled to cause WCF to log messages. This will also be addressed in a future release.
Workaround
• In the tool’s Configuration pane, expand the Diagnostics item if necessary.
• Click on the Message Logging item.
• In the Message Logging pane, set either LogMessagesAtServiceLevel or LogMessagesAtTransportLevel to True.
• Save the file.
