BrineSoft Script Editor
Script Editor - BrineSoft Online Help Prev Page Prev Page
Overview
What Is WSF
Why Use WSF
Scripting Languages
System Requirements
Command Line Options
Errors Handling
Find WSH Error
Bookmarks
Working with Bookmarks
Workspaces
Understanding Workspaces
Interim Workspace
Default Workspace
Workspace Files
Workspace Content
New Workspace Wizard
User Interface
Main Window
Find
Find in Files
Workspace Settings
Options
Object Properties
Replace Selection
Select Jobs
Tools
Select Scripting Language
Create a Windows Shortcut
Get Script File
New Project Wizard
Main Menu
Menu File
Menu Edit
Menu Find
Menu Workspace
Menu Project
Menu Run
Menu Options
Menu Tools
Menu View
Menu Window
Menu Help
Temporary Files
Temporary Files ~$
Temporary Files ~@
Working with Project Tree
Edit <job>
Edit <script>
Edit <object>
Edit <reference>
Edit <resource>
Edit <runtime>
Edit <comment>
Embedding All Scripts
Checking a Project
Working with Files
Open a Project or a Script
Run a Project or a Script
Save a Project or a Script
Close a Project or a Script
Miscellaneous
Microsoft Script Control
File ScriptEditor.xml
Purchase Script Editor
Register the Product
Registration Benefits
 BrineSoft Main Page | Script Editor Page | Download this Help File

Errors Handling

It is essential to know exactly what is wrong when a project or script execution fails. However, it is important to realize that it is dependent on the engine that processes the script:

Microsoft Script Control (embedded)
Editor highlights the line where the problem occured with the red color.
The cursor is positioned at the troubled syntax token.
The Script Errors list box at the bottom of the main window shows the description of the problem.
Clicking a line in the Script Errors list positions the cursor again.
Microsoft Script Control is not available for projects (*.wsf), but only for scripts (*.vbs, *.js, ...).

Windows Script Host - window based
The message box shows the description of the problem. The information contains line and column of the source code where the problem occured. Having this information use
Find WSH Error function to locate the problem in either a project or a script.

Windows Script Host - command line based
The problem description is written to the console. Editor leaves the console (DOS-box) open on purpose for this. The information contains line and column of the source code where the problem occured. Having this information use
Find WSH Error function to locate the problem in either a project or a script.

See Also
Find WSH Error, Workspace Settings, Options