# Windows Script Components

Windows Script Components provide you with an easy way to create Component Object Model (COM) components using scripting languages such as Microsoft® Visual Basic® Scripting Edition (VBScript) and other languages compatible with the ECMA 262 language specification (such as Microsoft® JScript® 2.0 and JavaScript 1.1). You can use script components as COM components in applications such as Internet Information Services (IIS), Microsoft® Windows Scripting Host (WSH), and any other application that can support COM components.

Script component technology is made up of the following:

- The script component run-time (Scrobj.dll).
- Interface handlers, which are components that extend the script component run-time. An interface handler is a compiled component (generally written in C++) that implements specific COM interfaces. When you install the script component run-time, you will receive the Automation interface handler, which makes it possible to call your script component from an .asp file.
- Your script component file (a.sct file). In your script component, you specify which interface handler you want to use. Your script component also defines the methods that can be called from an .asp file to accomplish the intended functionality.

Script components are an excellent technology for developing prototypes of COM components. Script components, like any other COM component, can be registered with Component Services if you intend for them to participate in transactions, or if you want to take advantage of the Component Services run-time environment. Because they are COM components, script components can access the ASP built-in objects.

For further details on script components, see the MSDN Online homepage. For further information on building a script component, see the Platform SDK. For specific examples of script components, see Using Components and Objects and the Platform SDK.

© 1997-2001 Microsoft Corporation. All rights reserved.