Windows Script File

A Windows Script File (WSF) is a file type used by the Microsoft Windows Script Host. It allows mixing the scripting languages JScript and VBScript within a single file, or other scripting languages such as Perl, Object REXX, Python, or Kixtart if installed by the user. These types of scripts may also be used to link many other external scripts together using a src parameter on the tag in a manner similar to HTML. Windows Script Files have the extension .WSF . A WSF makes reference to each script module in a very basic XML hierarchy as shown below, adhering to those standards outside the tags. Literal use of or inside your tags and similar challenges can be handled by the use of CDATA, as shown within the examples.

A Windows Script File (WSF) is a file type used by the Microsoft Windows Script Host. It allows mixing the scripting languages JScript and VBScript within a single file, or other scripting languages such as Perl, Object REXX, Python, or Kixtart if installed by the user. These types of scripts may also be used to link many other external scripts together using a src parameter on the tag in a manner similar to HTML. Windows Script Files have the extension .WSF . A WSF makes reference to each script module in a very basic XML hierarchy as shown below, adhering to those standards outside the tags. Literal use of or inside your tags and similar challenges can be handled by the use of CDATA, as shown within the examples. ' ' The first script module will produce a "divide by zero" error. Typically this would cause the script to end in the Windows Script Host but this modular method allows the script to continue and execute the second script module. function SortVBSArray(arr) {return arr.toArray().sort();} ' The output looks like this, sorted by ASCII code sequence: Original List of values: a,b,c,1,2,3,X,Y,Z,p,d,q JScript sorted in 0 seconds: 1,2,3,X,Y,Z,a,b,c,d,p,q const adLockBatchOptimistic = 4 MsgBox "The value of ""adLockBatchOptimistic"" is " & _ adLockBatchOptimistic & ".", vbInformation,"adLockBatchOptimistic" If your object documentation only refers to the constant's name and not the constant's value, you would have no way of knowing the value without the help of an Integrated development environment to tell you what they equate to. By using the WSF reference declaration, you can use the constants without declaring their values. The example below enumerates the values of several common constants in the ADO (ActiveX Data Objects) Recordset. ' Running the above script from a file with a .WSF extension, such as one named EnumerateConstantsADO.wsf , will produce the result shown below: ADO Recordset Values for Constants CursorTypeEnum Constants* -1 adOpenUnspecified 0 adOpenForwardOnly 1 adOpenKeyset 2 adOpenDynamic 3 adOpenStatic LockTypeEnum Constants* -1 adLockUnspecified 1 adLockReadOnly 2 adLockPessimistic 3 adLockOptimistic 4 adLockBatchOptimistic In addition, using the object reference to expose the constants makes writing the script more like writing in a standard programming language. In fact, the contents of the sample script, written in VBScript, will actually compile into a Visual Basic program and run the same way as long as that program uses the same reference to ADODB.

Text derived from https://en.wikipedia.org/w/index.php?oldid=1369018481 under CC BY-SA 4.0; modifications have been made.