Talk:Windows Script Host

message: 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)
thread_title: The different parts

message: 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 124.191.124.102 (talk) 22:54, 8 March 2008 (UTC)
replies: text: These are two quite different topics, in my opinion. DonToto (talk) 03:10, 30 June 2010 (UTC)
replies: text: Absolutley! WSH is a platform, that can be scripted by VBScript as well as others. VBScript just happens to be the most commonly used ActiveScripting language for system-administrators and has been pushed hard on them by Microsoft. At least it was like that in the heyday of the WSH. Merging it with the VBScript article would mean, that we could merge it with the Javascript, Python, Perl, Lua or Ruby article just as well. I am strongly opposed to this, simply because it would be factually wrong.2003:87:4A32:90D7:ED8B:D11F:E01F:B114 (talk)  —Preceding undated comment added 17:27, 5 March 2017 (UTC)
thread_title: Client Side VBScript

message: I think for a programming language that is highly important  —Preceding unsigned comment added by 81.184.58.60 (talk) 11:47, 26 April 2008 (UTC)
replies: text: This has been done in a previous edit. DonToto (talk) 03:10, 30 June 2010 (UTC)
thread_title:  Add an example 

message: The abbreviation WSH is not introduced before its first use. Shouldn't it?
--Mortense (talk) 13:34, 25 January 2010 (UTC)
replies: text: Agreed. This has now been done.DonToto (talk) 03:10, 30 June 2010 (UTC)
thread_title:  WSH not introduced 

message: 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)
thread_title: Available scripting engines

message: Which versions of ECMAScript do the different versions of JScript implement? --80.167.190.83 (talk) 08:39, 15 August 2012 (UTC)
thread_title:  ECMAScript Version 

message: Looks like the current name is "Windows Based Script Host" or "Windows-based Script Host" , not sure as of when. JeepdaySock (AKA, Jeepday) 13:45, 20 November 2012 (UTC)
thread_title: Windows Based Script Host

message: Activating Windows Script Host Editor-Dude (talk) 16:55, 2 March 2018 (UTC)
thread_title:  Activation 

message: So in addition to ASP, IIS, Internet Explorer, CScript and WScript, the WSH can be used to automate and communicate with any Windows application with COM and other exposed objects, such as using PerlScript to query Microsoft Access by various means including various ODBC engines and SQL, ooRexxScript to create what are in effect Rexx macros in Excel, Quattro Pro, Microsoft Word, Lotus Notes and any of the like, the XLNT script to get environment variables and print them in a new TextPad document, The VBA functionality of Microsoft Office, Open Office(as well as Python and other installable macro languages) and Corel WordPerfect Office is separate from WSH engines although Outlook 97 uses VBScript rather than VBA as its macro language.[8]
I paraphrased the above sentence for clarification as shown below:
 
So in addition to ASP, IIS, Internet Explorer, CScript and WScript, 
the WSH can be used to automate and communicate with any Windows application with COM and other exposed objects, such as:
1. using PerlScript to query Microsoft Access by various means including various ODBC engines and SQL, 
2.ooRexxScript to create what are in effect Rexx macros in Excel, Quattro Pro, Microsoft Word, Lotus Notes and any of the like, 
3.the XLNT script to get environment variables and print them in a new TextPad document, 
The above sentence should end at the phrase #3.
The following should be a new sentence because it has the capital letter "T" at the beggining.
The VBA functionality of Microsoft Office, Open Office(as well as Python and other installable macro languages) and Corel WordPerfect Office is separate from WSH engines although Outlook 97 uses VBScript rather than VBA as its macro language.[8]
YOSHIYUKI OGAWA (talk) 10:34, 27 February 2019 (UTC)
thread_title:  Punctuation error?