Microsoft provides several environments for scripting COM objects: Active Server Pages, Windows Script Host, and so on. Independent software vendors (ISVs) can also license Microsoft scripting engines for use in their applications. For example, an ISV creating a word processor might want to add a macro language to the application so users could automate simple tasks. By licensing a scripting engine, the ISV can use a language such as VBScript or JScript as the application's macro language.
In addition to licensing VBScript and JScript scripting engines, ISVs can write their own ActiveX scripting engines. These scripting engines can then be plugged into any host environment that supports the ActiveX scripting engine standard. For example, an ISV might write a PerlScript scripting engine and install it on an ASP server, thus enabling the ASP server to process PerlScript scripts.
Related topics
Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
