SamScrpt.exe sample demonstrates implement Active Debugging in an ActiveX Script Engine built in straight C++

SamScrpt.exe is a sample that demonstrates how to implement Active Debugging in an ActiveX Script Engine built in straight C++. It is designed to demonstrate some of the more advanced features of Active Debugging, such as expression evaluation and variable windows.

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


SamScrpt.exe (http://download.microsoft.com/download/vc60std/demo1/6.0/nt4/en-us/samscrpt.exe)

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base: 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 to prevent any unauthorized changes to the file.

This sample demonstrates how to build an ActiveX Script Engine, including support for Active Debugging. ActiveX Scripting allows Hosts such as Internet Explorer to execute scripts without having to be concerned with the actual implementation of the language engine. Active Debugging builds on Active Scripting and enables debugger host applications, like the 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.

While every attempt has been made to make this sample engine accurate, it is not a commercial quality application. Microsoft does not support the use of this engine in any capacity.

Installation Instructions

1. Add the following paths to the Include directories in the \Tools\Options\ directory. Replace ... with the path where SampleScript was installed.
   
   ...\SampleScript\
   ...\SampleScript\Interpreter\
   ...\SampleScript\Active Script Engine\
   ...\SampleScript\Active Debugging\
   ...\SampleScript\scripting\
   
   Drag the ...\SampleScript\scripting\ path to the top of the list so it is checked first.
2. Add the following paths to the library directories in the \Tools\Options\ directory. Replace ... with the path where SampleScript was installed.
   
   ...\SampleScript\scripting\
   
   Drag the ...\SampleScript\scripting\ path to the top of the list so it is checked first.
3. From the Project menu, click Settings and click the Link tab. In the Object/Library modules, make sure that ad1.lib is referenced. This file contains GUIDs necessary for Active Debugging.
4. Build the project. You need to modify the Objsafe.h file in the Visual C++ Include directory if you get 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
   						

5. Register the SampleScript.dll by using Regsvr32.
6. Copy the English.dll file to the same directory as SampleScript.dll.

For additional information about Active Debugging, click the article number below to view the article in the Microsoft Knowledge Base: