Information and Guidelines for Visual J++ Programmers

See Also   

To access the Visual Studio Analyzer programming interfaces from within Visual J++, you need to add COM wrappers for the libraries in which they reside to your Visual J++ project. Once you add the COM wrappers, Visual J++ creates Java classes for each programming interface.

To add the Visual Studio Analyzer libraries

  1. Click the Project menu, and then click Add COM Wrapper.

  2. In the Installed COM Components box, select the check box for the following two libraries:
  3. Click OK.

These libraries give you access to the event source installer and in-process event creator classes.

If the Visual Studio Analyzer libraries are not listed in the COM Wrappers dialog box, make sure that Visual Studio Analyzer is installed on your machine. If Visual Studio Analyzer is installed but the libraries are not listed in the COM Wrappers dialog box, you can browse for the two DLLs you need, vaesa.dll and vaiea.dll. These DLLs are located in C:\Program Files\Microsoft Visual Studio\Common\Tools\VS-Ent98\Vanalyzr if you use the default installation location.

Constants for Visual Studio Analyzer Predefined Events

Visual Studio Analyzer ships with a number of predefined events. These events are identified by global unique identifiers (GUIDs) and must be referred to by their GUID each time you use them in code. However, you can make using these predefined events a little easier for yourself by creating constants for these events and saving them in a global file. You can then include that file in your projects that contain code for customizing Visual Studio Analyzer.

The predefined events and their GUIDs are listed in file vaids.h. This file contains C++ declarations. You can use this file as a source to create your file of Java constants.

For example, the DEBUG_EVENT_CALL predefined event appears in vaids.h as follows:

DECLARE_GUID(DEBUG_EVENT_CALL, 6c736d61, bcbf, 11d0, 8a, 23, 00, aa, 00, b5, 8e, 10);

In your file, use the following format:

static String DEBUG_EVENT_CALL = "{6c736d61-BCBF-11D0-8A23-00AA00B58E10}";