WSCRIPT與CScript區(qū)別

窗口中運(yùn)行，WSCRIPT;命令行中運(yùn)行，CScrip;
    cscript因?yàn)榘演敵龇胚M(jìn)了控制臺(tái) 所以可以對(duì)它重定向 方便程序調(diào)用
    wscript直接用窗口輸出 適合調(diào)試程序和編寫(xiě)小工具 在windows下不用cmd的話cscript的輸出會(huì)一閃而過(guò) 大多數(shù)情況下，列在下表中的選項(xiàng)適用于 WScript.exe 和 CScript.exe。例外情況會(huì)加以注釋。

參數(shù)                      說(shuō)明
//B                       批處理模式；隱藏用戶(hù)提示和腳本錯(cuò)誤在命令行中的顯示。默認(rèn)模式是交互模式。
//D                       打開(kāi)調(diào)試程序。
//E:engine                用指定的腳本引擎執(zhí)行腳本。
//H:CScript或 //H:Wscript 將 CScript.exe 或 WScript.exe 注冊(cè)為運(yùn)行腳本的默認(rèn)應(yīng)用程序。如果未指定，則將 WScript.exe 假設(shè)為默認(rèn)應(yīng)用程序。
//I                       默認(rèn)。交互模式；允許顯示用戶(hù)提示和腳本錯(cuò)誤。與批處理模式相反。
//Job:<JobID>             從 .wsf 文件運(yùn)行指定的 JobID。
//logo                    默認(rèn)。顯示標(biāo)題。與 nologo 相反。
//nologo                  防止在運(yùn)行時(shí)顯示執(zhí)行標(biāo)題。默認(rèn)設(shè)置是 logo。
//S                       保存該用戶(hù)的當(dāng)前命令行選項(xiàng)。
//T:nn                    啟用超時(shí)：腳本可以運(yùn)行的最大秒數(shù)。默認(rèn)設(shè)置是無(wú)限制。//T 參數(shù)通過(guò)設(shè)置定時(shí)器來(lái)防止腳本執(zhí)行過(guò)度。當(dāng)執(zhí)行時(shí)間超過(guò)指定值時(shí)，CScript 用 IActiveScript::InterruptThread 方法中斷腳本引擎，并終止過(guò)程。
//U                       用于 Windows NT 和 Windows 2000，強(qiáng)制命令行以 Unicode 格式輸出。CScript 無(wú)法決定以 Unicode 還是以 ANSI 輸出；默認(rèn)設(shè)置為 ANSI。
//X                       在調(diào)試程序中啟動(dòng)該程序。
//?    

Script Hosts
The script host initiates and coordinates the running of your script; it reads your script file and interacts with components of the WSH environment and any COM objects required by the script. It is also the responsibility of the script host to determine which language engine to use when running the script. For example, if the script has a .vbs extension, the script host will load the VBScript language engine and begin working with that engine to execute the code.

The WSH environment includes two script hosts: the console-based CScript and the GUI-based WScript. The two script hosts provide nearly identical capabilities, and in most cases, it does not matter which of the script hosts you use to run your scripts.

The two exceptions lie in how you interact with a script; that is, how you get information into a script (input) and how the script displays information it has retrieved (output). In general, CScript receives input from the command prompt and displays output in a command window. WScript, by contrast, receives input through a graphical dialog box and displays output in a graphical message box.

Otherwise, the two script hosts are largely identical: If you have a script that does not require user interaction, you can run that script under either CScript or WScript. For example, the following script maps a network drive. Because it neither requires input nor displays output, it runs exactly the same under either script host:

Set objNetwork = Wscript.CreateObject("WScript.Network")objNetwork.MapNetworkDrive "g:", "\\atl-fs-01\Sales"
On the other hand, the following script which displays a series of messages runs much differently under CScript (where the messages are displayed as individual lines within a command window) and WScript (where the messages are displayed as a series of message boxes). If you are interested in seeing the difference for yourself, copy the script into Notepad, save it with a .vbs file extension, and then run it under both CScript and WScript. (For more information about running scripts under a script host, see "Running WSH Scripts" later in this chapter.)

最新評(píng)論