Windows Script File

Microsoft has a very simple article about Windows Script Files located here: Using Windows Script Files

The benefits of a Windows Script Files(WSF):

As explained at the URL above, WSF allows you to make your scripts more modular and independent. This includes mixing Perl, JScript, and VBScript within one file. This allows developers of different skill sets to work together. You may also reference files externally so a WSF can be used to link many scripts together.

I find them useful for diagnosing errors. Their modular nature prevents one script reference from interfering with another. Here is a WSF example with one module that produces an error and one does not:

<job id="Partially works">
  '** This will not work
  <script language="VBScript">
        WScript.echo 4/0 ' Oh boy! You cannot divide by zero...
  </script>
  '** This will work... definitely...
  <script language="VBScript">
        WScript.echo "Hello Scripters!" & vbNewline & _
                     "Fantastic! It worked!"
  </script>
</job>

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.

---