The native support for tracing in WCF is very good but as sometimes is the case is missing a functionality that I happen to need right now: The ability to rotate the trace files or in other words automatically switching to a new trace file based on a time based criteria.

Why do I need this?

I’ve been working on a project that has come to rely heavily in the trace files as a way to keep track of all the calls made by partners. If something goes wrong the trace files are the place to go to find out what really happened. Tracing, which in my opinion should only be enabled to troubleshoot a given problem, is now always on and the trace file gets big, really big, so finding a given message comes with the price of downloading this trace file and then searching for a given text.

The Service Trace Viewer Tool does a decent job opening these big trace...

Two days ago I tried to deploy to a production environment a WCF service and got the following error:
 
System.ServiceModel.EndpointNotFoundException
There was no channel actively listening at 'http://somehostnameIdidntrecognize.local/services/myservice.svc'. This is often caused by an incorrect address URI. Ensure that the address to which the message is sent matches an address on which a service is listening.