Getting traces for .NET apps when you cannot modify the application

added by Paul Wheeler
8/20/2014 12:43:22 PM


One of the biggest pains of .NET applications going against Exchange is getting detailed logs.  Using a tracing tool like Fiddler is great since it will SSL decode traffic, however it won't capture traffic from a .NET application running on the same box unless that application can set its proxy settings to that of Fiddler.  Having a client app modified to give the ability to set proxy settings is time consuming and often not possible.  However, you don’t necessarily need to go through that given that a config file can be created in the same folder as the applications .NET executable and can be used to have the traffic logged to a file and even provide proxy setting defaults.