Microsoft KB Archive/216073

= How to implement Active Debugging in ATL ActiveX Script Engine =

Article ID: 216073

Article Last Modified on 4/20/2005

-

APPLIES TO


 * Microsoft Visual C++ 5.0 Enterprise Edition
 * Microsoft Visual C++ 6.0 Enterprise Edition
 * Microsoft Visual C++ 5.0 Professional Edition
 * Microsoft Visual C++ 6.0 Professional Edition
 * Microsoft Visual C++ 6.0 Standard Edition

-



This article was previously published under Q216073



SUMMARY
The 4thScrpt.exe sample demonstrates how to implement Active Debugging in an ActiveX Script Engine built with Active Template Library (ATL). The sample is designed to supplement the Active Debugging documentation available on the Microsoft Developer Network (MSDN).

This sample demonstrates how to add Active Debugging support to an ActiveX Script Engine. Active Debugging builds on Active Scripting and enables debugger host applications, such as Microsoft Script Debugger, to provide comprehensive, language-independent testing, and error correcting capabilities. Functionality, such as breakpoints, expression evaluation, and data monitoring, are all possible through the Active Debugging interfaces. Active Debugging also makes it possible to debug multiple scripts in different languages concurrently, making cross-language issues easier to locate and correct.



MORE INFORMATION
The following file is available for download from the Microsoft Download Center:

Download the 4thScrpt.exe package now. Release Date: Jan. 20, 2000

For more information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

To compile the 4thScrpt.exe file
 In Visual C++, add a new include directory by clicking Options in the Tools menu. Select the Directories tab, and show directories for Include files. Click in the Directories window, and then add a path to the Scripting folder of this sample. Drag this path to the top of the list so that it is checked first. On the Directories tab, show directories for Library files. Click in the Directories window and add a path to the Scripting folder of this sample. Drag this path to the top of the list so that it is checked first. This folder contains headers and libraries needed to compile Active Scripting and Active Debugging projects. On the Project menu, click Settings and then click the Link tab. In the Object/Library modules, make sure that the Ad1.lib file is referenced. This file contains GUIDs necessary for Active Debugging.  Build the project. You must modify the Objsafe.h file in the Visual C++ Include directory if you receive the following error messages:

error C2065: 'INTERFACE_USES_DISPEX' : undeclared identifier

error C2065: 'INTERFACE_USES_SECURITY_MANAGER' : undeclared identifier

Find the definitions for the Option bits for IObjectSafety, and add definitions for INTERFACE_USES_DISPEX and INTERFACE_USES_SECURITY_MANAGER, as shown below. These bits are required by Internet Explorer. // Option bit definitions for IObjectSafety: #define INTERFACESAFE_FOR_UNTRUSTED_CALLER  0x00000001 // Caller of interface may be untrusted #define INTERFACESAFE_FOR_UNTRUSTED_DATA    0x00000002 // Data may be untrusted #define INTERFACE_USES_DISPEX               0x00000004 // Object knows to use IDispatchEx #define INTERFACE_USES_SECURITY_MANAGER     0x00000008 // Object knows to use IInternetHostSecurityManager Once the project has compiled, the engine registers itself. See the ForthScript.txt file for more information about this sample. 

