COM and ActiveX Debugging
Applies to: 
Visual Studio 
Visual Studio for Mac
Note
This article applies to Visual Studio 2017. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here
This section provides tips on debugging COM applications and ActiveX controls.
In This Section
COM Server and Container Debugging Mentions special considerations when debugging COM applications. Issues include: debugging a COM server and container using two projects within the same solution, tracing into calls that go across process boundaries, setting breakpoints in callback functions, and stepping across and into containers and servers.
How to: Debug an ActiveX Control Contains information on debugging ActiveX controls. This includes: specifying a container for the debug session to see how the code in your ActiveX control executes, debugging a data-bound ActiveX control, simulating a particular container, and stepping into the container's code.
COM Debugging Tools Lists viewers and sample applications that may be useful in debugging your COM application.
Related Sections
First look at the debugger Provides links to the larger sections of the debugging documentation. Information includes: what's new in the debugger, settings and preparation, breakpoints, handling exceptions, edit and continue, debugging managed code, debugging C++ projects, debugging COM and ActiveX, debugging DLLs, debugging SQL, and the user interface references.