Breakpoint Object

Home Page (Objects) |  Overview |  FAQ |  Reference

The Breakpoint object represents a breakpoint that is set for debugging purposes.

The Breakpoint object has the following properties and methods:

Using a Dual Interface to Access This Object

This section about dual interfaces is useful for writing add-ins or automating Developer Studio across processes. This section is not applicable to writing VBScript macros.

The Breakpoint object implements the IBreakpoint dual interface. Through this interface, add-ins can directly access the members (properties, methods, and events) of this object and can employ early binding to make calls into these members faster at run time.

Add-ins written in Visual C++ can access members of the Breakpoint object by using the header files in Vc98\Include\objmodel. However, if you use the Developer Studio Add-in Wizard to create an add-in, the wizard automatically includes these header files in your source code.

The following header files are used for the Breakpoint object:

dbgauto.h – Declares the dual interfaces.

dbgguid.h – Declares the GUIDs used to identify the interfaces.

dbgdefs.h – Declares additional information needed to use the interfaces, such as error IDs and enumerated constants.

Add-ins written in Visual Basic can access members of the Breakpoint object by using the Debugger type library, located in msdev98\bin\ide\devdbg.pkg.

Note   In the Visual Basic References dialog box (Project menu, References command), the names of the type libraries begin with "Visual C++ 6.0" for Visual C++ version 6.0. For Visual C++ version 5.0, the names begin with "Visual Studio '97."