• 2

System.Net and related.

Summary: Useful logging option to track problems on Sockets, Remoting Channel, Web Requests and HttpListener.

Platform: .Net 2.0

Details:

How to: Configure Network Tracing
http://msdn2.microsoft.com/en-us/library/ty48b824.aspx

Enabling Network Tracing
http://msdn2.microsoft.com/en-us/library/a6sbz1dx.aspx

ADO.Net Managed Provider ETW Tracing

Summary: Very powerful tracing with details on API invocations, 1st chance exceptions. Next generation of high performance tracing.

Platform: .Net 2.0 with Windows 2003 SP1 or Windows XP SP2

Details:

Tracing Data Access
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnadonet/html/tracingdataaccess.asp

System.Xml Serialization.

Summary: Leave the temporary auto-generarted XML serialization code behind for easier debugging XML serialization problems.

Platform: .Net 1.0 above

Details:

PRB: You Receive a "System.IO.FileNotFoundException" Error When the Client Application Calls a Web Service
http://support.microsoft.com/?id=823196

Troubleshooting Common Problems with the XmlSerializer
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnxmlnet/html/trblshtxsd.asp

Visual Studio 2005 IDE Activity Log

Summary: Provide additional information for IDE crash issues.

Platform: Visual Studio 2005

Details:

/Log (devenv.exe)
http://msdn2.microsoft.com/en-us/library/ms241272.aspx

VSTS related

Team Foundation Server Component Trace

Summary: File based trace for TFS components.

Platform: Team Foundation Server

Details:

Global Web.Config File Settings in Team Foundation Server Components
http://msdn2.microsoft.com/en-us/library/ms400784.aspx

Enabling Trace for Team Foundation Server Components
http://msdn2.microsoft.com/en-us/library/ms400788.aspx

Team Build Service Log

Summary: Detailed log for troubleshooting Team Build Service problems.

Platform: Team Foundation Server

Details:

Please refer to the comment in the following file where Team Build Service is installed:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\tfsbuildservice.exe.config

Team Foundation Client Log

Summary: This log is useful for tracking problem, espcially performance problem with Team Explorer.

Platform: Team Foundation Server Client Components

Details:

There seems to be no formal document on this. Buck's blog has mentioned it:

How to measure performance using the web service performance dialog
http://blogs.msdn.com/buckh/archive/2006/09/25/performance_dialog.aspx

Apart from Buck's blog, the setting for the .Config file can also use a file based trace listener:

  <system.diagnostics>

    <switches>

      <add name="General" value="4" />

    </switches>

    <trace autoflush="true" indentsize="3">

      <listeners>

        <add name="myListener"

        type="Microsoft.TeamFoundation.TeamFoundationTextWriterTraceListener,Microsoft.TeamFoundation.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"

        initializeData="c:\devenv.log" />

      </listeners>

    </trace>

  </system.diagnostics>

WinForm related

IEHost Log

Summary: Trace for troubleshooting .Net WinForm component download hosted in IE.

Platform: .Net 1.0 above

Details:

HOW TO: Use the IEHost Log to Debug .NET Object Hosting in Internet Explorer
http://support.microsoft.com/?id=313892

System.Transactions

Summary: Useful for tracing internal Transaction code paths..

Platform: .Net 2.0

Details: