Today, Most of the .NET Developers/SOA Lovers have been really enjoying the Power of Windows Communication Foundation features. But, the hardest portion of WCF development is Tracing/Logging in Remote System(i.e., Production Server), however Microsoft has recommended to use SvcTraceViewer.exe to analyze diagnostic traces that are generated by WCF. Service Trace Viewer provides a way to easily merge, view, and filter trace messages in the log so that you can diagnose, repair, and verify WCF service issues. But, from my understanding or experience it is hard to find out the exact error log using SvcTraceViewer.exe in svcLog file(WCF Tracing file) and We have been using DebugViewer to trace the WCF log events or exceptions. I would like to describe the power of DebugViewer here interms of tracing/logging the Windows Communication Foundation output in the remote system (i.e., Production Server).
DebugView is an application that lets us monitor debug output on our local system, or any computer on the network that we can reach via TCP/IP. It is capable of displaying both kernel-mode and Win32 debug output(i.e., WCF output) so we don't need a debugger to catch the debug output WCF applications or device drivers generate, nor do we need to modify WCF applications or drivers to use non-standard debug output APIs. Simply execute the DebugView program file (dbgview.exe) and DebugView will immediately start capturing debug output. Note that if you run DebugView on Windows 2003/XP you must have administrative privilege to view kernel-mode debug output. Menus, hot-keys, or toolbar buttons can be used to clear the window, save the monitored data to a file, search output, change the window font, and more. Here is a screenshot of DebugView capturing Windows Communication Foundation debug output from a remote system.
.gif)
.gif)
lovedjohnysmith