Windows Script Components in IIS

Windows Script Components provide you with an easy way to create Component Object Model (COM) components using scripting languages such as Visual Basic Scripting Edition (VBScript) and other languages compatible with the ECMA 262 language specification (such as JScript 2.0 and JavaScript 1.1). You can use script components the same way you would use any COM component in an application such as ASP.

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.

Sometimes components need to access the ASP built-in objects (Server, Request, Response) to get information about the client request or to build the response. Components can access the ASP built-in objects by using the ObjectContext object. For more information, see Accessing ASP Built-In Objects from Components.

See Also


Creating Script Components for ASP

Accessing ASP Built-In Objects from Components