The Windows Scripting Host - dFPUG-Portal

Print Article
A quick word about debugging and handling errors
No programming environment is complete without a full-featured debugging environment. The WSH is no exception, as it also
has a full-featured debugger. As far as error handling is concerned, VBScript doesn't have a global error handler. Rather,
errors need to be handled on an in-line basis. The following code demonstrates how to deal with errors on an in-line basis:
On Error Resume Next
dim objxl
Set objXL = WScript.CreateObject("Excel.Application")
objxl.foo ' reference a non-existent Excel Method
If Err.Number > 0 Then
Call ErrorProc
End If
Sub ErrorProc
msgbox err.description
End Sub
If no error trapping exists, you'll be prompted with a dialog box asking if you wish to debug the application. Figure 1 illustrates
how the code will appear in the script debugger.
Figure 1. The Microsoft Script Debugger uses the same IDE as Visual InterDev and Visual J++ 6.0.
The WSH objects
There are two primary objects contained within the WSH. The following code illustrates how these objects can be created:
WSHshell = CreateObject("Wscript.Shell")
WSHNetwork = CreateObject("Wscript.Network")
Both the shell and network objects are hosted by the wshom.ocx ActiveX Control.
Complete documentation for the WSHShell and WSHNetwork Objects can be found by navigating to the following URLs:
http://www.microsoft.com/iis/support/iishelp/iis/htm/asp/wsho7t84.htm for the WSHShell object
http://www.microsoft.com/iis/support/iishelp/iis/htm/asp/wsho20qc.htm for the WSHNetwork object
Seite 2 von 6
Shell object properties and methods
Environment
This property provides access to the environment collection. Information such as number of processors, paths, OS, and so
forth can be determined from this collection.
http://foxtalknewsletter.com/ME2/Audiences/Segments/Publications/Print.asp?Module=...
31.01.06