Active Scripting (formerly known as ActiveX Scripting) is the technology used in Windows to implement component-based scripting support. It is based on OLE Automation (part of COM) and allows installation of additional scripting engines in the form of COM modules.
Uses and history
The Active Scripting technologies were first released in 1996, with the release of the Microsoft Internet Explorer 3.0 (August 1996) and Internet Information Services 3.0 products (December 1996).
Usual applications of Active Scripting include
For many of the above uses, Active Scripting is an addition to Windows that is similar to the functionality of Unix shell scripts, as well as an incremental improvement upon batch files (command.com), Windows NT style shell scripts (cmd.exe) and, by way of
The interfaces to Active Scripting engines are public, so any developer can create applications that are programmable in Active Scripting languages as well as engines for additional languages.
Active Scripting engines are available for several languages. Some of the most popular include:
- ActivePerl – Perl
- ActivePHP and PHPScript for PHP
- REXX(multiple versions)
- Visual Basic for Applications (VBA) for Windows; and requires Microsoft Office, or other software packages that are VBA-programmable.
In Windows, CScript.exe at the command line and WScript.exe running in the GUI are the main means of implementation of installed Active Script languages. Clicking on an icon or running from the command line, a script, the Run dialogue, etc. will by default run a plain text file containing the code. A Windows Script File (.wsf) is an XML file that can contain more than one script in more than one language in addition to other elements, and are executed by the Windows Script Host.
The third-party shell Take Command can, as of version 10, be configured for direct interoperability with the script host and its installed engines; a WSH engine based on the Take Command language is reportedly now in development.
Some software such as SecureCRT use the WSH functionality to allow automation by means of any installed scripting engine.
The script host, related components, and engines are able to be integrated into and called from Windows applications just like any other component.
Active scripting is regarded complete, and no longer under active development by Microsoft. However, the technology is still being supported by Microsoft's Sustaining Engineering Team, which is responsible for bug fixes and security enhancements. Furthermore, scripting engines will continue to be shipped with future releases of Microsoft Windows and IIS.
Originally, the .NET Framework had a scripting technology of its own and a separate scripting IDE called Visual Studio for Applications (VSA),
Microsoft has also introduced
- ^ Rumours of VBScript's Death Have Been Greatly Exaggerated, on Eric Lippert's Blog Fabulous Adventures In Coding on MSDN (April 09, 2004).
- ^ Script Happens .NET, article by Andrew Clinick of Microsoft Corporation, in Scripting Clinic on MSDN (July 25, 2001).
- ^ Microsoft Takes Wraps Off VSA Development Technology Archived 2007-12-17 at the Wayback Machine, by Scott Bekker on Redmondmag.com (January 16, 2001).
- ^ a b VSA scripting in .NET Archived 2007-02-11 at the Wayback Machine, by Mark Belles on The Code Project.
- Windows Script Interfaces – Active Scripting documentation.
- Future of VBScript Language – Information about the future of Active Scripting technologies.