I hope you never need it, but it is possible to do some real low level tracing to see what network communications are happening inside your .NET app.
To enable this, you can add diagnostics at the System.NET level:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<system.diagnostics> | |
<sources> | |
<source name="System.Net" tracemode="includehex" maxdatasize="1024"> | |
<listeners> | |
<add name="System.Net"/> | |
</listeners> | |
</source> | |
<source name="System.Net.Sockets"> | |
<listeners> | |
<add name="System.Net"/> | |
</listeners> | |
</source> | |
<source name="System.Net.Cache"> | |
<listeners> | |
<add name="System.Net"/> | |
</listeners> | |
</source> | |
</sources> | |
<switches> | |
<add name="System.Net" value="Verbose"/> | |
<add name="System.Net.Sockets" value="Verbose"/> | |
<add name="System.Net.Cache" value="Verbose"/> | |
</switches> | |
<sharedListeners> | |
<add name="System.Net" type="System.Diagnostics.TextWriterTraceListener" initializeData="c:\tracelogs\network_trace.log"/> | |
</sharedListeners> | |
<trace autoflush="true"/> | |
</system.diagnostics> |