Share via

Auto Debug is disabled

  • Article

The information in this article applies to:

  • Visual Studio 2005 Team Foundation Server

  • Visual Studio Team System 2008 Team Foundation Server

  • Application-tier server

  • Data-tier server

  • Health check

The Best Practices Analyzer tool for Team Foundation Server reads the value for the following registry key to determine whether a post-mortem debugger is defined:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger

A best-practices message appears if the value of this key is not defined. This key specifies a post-mortem debugger for unhandled user mode exceptions. By using such a debugger, you can see what went wrong in the code by examining where the program caused the fault, in addition to the condition of registers, memory, and the stack.

As a best practice, you should define a post-mortem debugger for the computers where you installed Team Foundation Server. By default, Dr. Watson is defined as the post-mortem debugger.

Note

The value for the Debugger key is changed when you install Team Foundation Server because it registers itself as an available debugger. Then Team Foundation Server prompts the user to specify the debugger when an exception occurs.

To resolve this issue, use Registry Editor to change the value for the Debugger key. For more information, see "Specifying the Debugger for Unhandled User Mode Exceptions" on the Microsoft Web site.

Important noteImportant Note:

If you edit the registry incorrectly, you might severely damage your system. Before you make any changes to the registry, you should back up any valued data on the computer.

See Also

Other Resources

Hardware and Platform Issues