VBScript – To Check your Versions

Introduction to Checking Version Numbers

There are occasions when you need to investigate the VBScript version number.  For example, if you have old clients with version 2.x., VBScript commands may not work.  To give a specific example you may want a script to pause, in which case you could use WScript.Sleep.  The problem is that this .Sleep property was only added in WSH version 5.1.  If you are sure all your clients are XP, then no problem, but if the scripts are going to run on Windows 9x machines you may wish to check the version with a simple script.

The first bonus of checking version numbers is that investigation reveals just how many components are involved in a VBscript, for instance, Windows Scripting Host (WSH) and also VBScript itself.

Topics for Checking Version Numbers

• Example 1 – VBScript to Check the WSH Version
• Example 2 – VBScript to Check the WSH Version and Build Number
• Example 3 – VBScript to Check the VBScript Version
• Summary of Checking Version Numbers

Example 1 – VBScript to Check the WSH Version

VBScripts need a shell called Windows Scripting Host (WSH).  Examples 1 and 2 are designed to extract the version information about WSH.  (In Example 3 we switch to the VBScript itself.)

Prerequisites

This is a script that will execute equally well on a Windows server or an XP machine.

Instructions for Checking WSH Version

1. Copy and paste the example script below into notepad or a VBScript editor.
2. Save the file with a .vbs extension, for example, WSH.vbs 
3. Double click WSH.vbs and read the version in the message box.

Sample VBScript to Check the WSH Version

VBScript Tutorial – Learning Points

Note 1:  I am expecting the script to return a WScript version of 5.6 

Note 2:  Here we have a mixture of literals: "WSH Version: " and variables: WScript.Version.  Paying attention to detail pays off.  In this instance, notice how the space before the closing quotes makes the output easier to understand.

Note 3: Time and time ampersand (&) is your friend in joining VBScript components.  I have to confess that I am often concentrating so hard on the more difficult commands that I forget the ampersand.  When I make this sin of omission, WSH brings me up sharply with a message: Code 800A0401 – Expected end of statement.

Guy Recommends: Permissions Analyzer – Free Active Directory Tool

I like thePermissions Monitor because it enables me to see quickly WHO has permissions to do WHAT.  When you launch this tool it analyzes a users effective NTFS permissions for a specific file or folder, takes into account network share access, then displays the results in a nifty desktop dashboard!

Think of all the frustration that this free utility saves when you are troubleshooting authorization problems for users access to a resource.  Give this permissions monitor a try – it’s free!

Download Permissions Analyser – Free Active Directory Tool

Example 2 – VBScript to Check the WSH Version and Build Number

Script to Display WSH and File Information

VBScript Tutorial – Learning Points

Note 1:  Most of the time, I only use WScript.Echo and perhaps WScript.Quit, I was surprised to discover that WScript has so many properties, for example .Version, .BuildVersion and even .ScriptName.  From a teaching perspective, the message is that objects have properties, which we access with the syntax object.dot.property.  Incidentally, my WScript build number was 8827.

Note 2:  One potential problem with VBScript commands is that they are more than 80 characters long.  Moreover, VBScript has no concept of word-wrap, so if you just continue the same instruction on the next line, VBScript will interpret your intention as two instructions and not one.  Fortunately, there is a solution, the underscore (_).  What underscore does is tell VBScript that the command has not yet finished, but to read the rest of the same command on the next line.

Note 3:  Observe the command vbcr, this makes a carriage return in the actual output message box.  It is purely cosmetic, but it often makes output easier to understand.

Example 3 – VBScript to Check the VBScript Version

As we will see our scripts require both VBScript itself and also WSH shell.  This script concentrates on the VBScript executable.  Incidentally, you can confirm the information by checking the information directly on cscript.exe in the Windows\System32 folder.

Please note that this script checks VBScript and is different from Example 1 and 2 which report version numbers for WSH.  You will probably notice how ScriptEngineMajorVersion and ScriptEngineMinorVersion replace WScript.Version.

Sample Script to Check the VBScript Version

VBScript Tutorial – Learning Points

Note 1:  Unlike example 1 this script needs to build the version number from two numbers, and artificially concatenate a dot in between.

Challenge:

These three scripts are so short you could easily bolt them all together – could not you?  This would mimic real life situations where you build scripts in stages, get them working then bolt them together to create the production script.

Summary of Checking Version Numbers

From a practical point of view, it may be necessary to check the version of VBScript or WSH.   From a pure scripting point of view there are parallels with English.  When composing ordinary English, many of us – me included, are unsure when to use a semi-colon; a dash is even harder to master.  Syntax is equally important in VBScript, therefore take a minute or two to master the underscore (_) and vbcr.

See Also

• Getting Started
• VBScript Home