Talk:Windows Script Host
|WikiProject Computing / Software||(Rated Start-class)|
|WikiProject Microsoft Windows / Computing||(Rated Start-class, Mid-importance)|
The different parts
WSH is made of 3 distinct parts:
- WScript.* Automation classes (WScript.Shell and WScript.Network), available to all automation hosts, but adding much needed features to WSH.
- WScript.exe, the GUI WSH host.
- CScript.exe, the console WSH host.
Both WScript.exe and CScript.exe includes a "WScript" object (aka "WSH", both names reference the same live objects) available to any script engine loaded in WSH and providing basic functions like text output and arguments parsing.
Note the WScript objects exposed by WScript and CScript, altough they implement the same interface, are not the same objects, WScript in WScript.exe is designed for GUI operations, and its .Echo method generates a dialog, while WScript in CScript.exe is designed for console operations, and its .Echo method generates stdout text in the console window. Another notable difference is that the .StdIn, .StdOut and .StdErr properties of the WScript object are only available in the CScript.exe version.
PhMajerus 17:16, 13 April 2007 (UTC)
Client Side VBScript
There is a proposal to merge the Wikipedia entry for VBScript with Windows Script Host. Please note that VBScript can also run as client script. —Preceding unsigned comment added by 22.214.171.124 (talk) 22:54, 8 March 2008 (UTC)
Add an example
WSH not introduced
The abbreviation WSH is not introduced before its first use. Shouldn't it?
Available scripting engines
Could someone please explain what is the intention of the first two columns, Name, and Language. It doesn't seem to make sense, e.g. Perl is not PerlScript, etc. But perhaps I am missing something? DonToto (talk) 03:10, 30 June 2010 (UTC)