Web service development is not so difficult as you may imagine if you know some tips. One of this tips is WCF tracing! Creating your web service you may debug it and never get reaction because debug breakpoints are not reachable and problems are inside settings of web service or client. Wrong configuration parameters of client is problem of communication between partners.
So, we have a medicine for you: WCF tracing.
1. Open WCF config editor. Write svcconfeditor command in commandline or use “Service Configuration Editor” link in Microsoft Visual Studio 2010 folder.
Image may be NSFW.
Clik here to view.
2. Open your config file.
Image may be NSFW.
Clik here to view.
If you use Sharepoint and it’s application folder (12 or 14) to create your web services, use web.config that is saved in inetpub folder of IIS.
Default folder:C:\inetpub\wwwroot\wss\VirtualDirectories\[Number of web app port]\
3. Correct Diagnostics part of config.
Image may be NSFW.
Clik here to view.
Switch on MessageLogging or/and Tracing and make specific rules.
4. Make iisreset
5. Open trace files with svctraceviewer and find your problem (highlighted with red colour).
Image may be NSFW.
Clik here to view.
Links:
1. Bacis info (http://blogs.msdn.com/b/madhuponduru/archive/2006/05/18/601458.aspx)
2. Information about trace levels (http://msdn.microsoft.com/en-us/library/ms732023.aspx)
3. WCF Tracing FAQs (http://www.codeproject.com/Articles/36031/WCF-Tracing-FAQs)
Image may be NSFW.
Clik here to view.
Image may be NSFW.Clik here to view.
