BrineSoft Script Editor
Script Editor - BrineSoft Online Help Prev Page Prev Page
What Is WSF
Why Use WSF
Scripting Languages
System Requirements
Command Line Options
Errors Handling
Find WSH Error
Working with Bookmarks
Understanding Workspaces
Interim Workspace
Default Workspace
Workspace Files
Workspace Content
New Workspace Wizard
User Interface
Main Window
Find in Files
Workspace Settings
Object Properties
Replace Selection
Select Jobs
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
Microsoft Script Control
File ScriptEditor.xml
Purchase Script Editor
Register the Product
Registration Benefits
 BrineSoft Main Page | Script Editor Page | Download this Help File

New Workspace Wizard

Workspace name

Enter a short but descriptive name for the new Workspace. This name will appear in combo boxes and menus, and it is the name of the Workspace file (*.wsf) at the same time.


In most cases each Workspace represents a new project (a new task) and therefore it will have its files in a separate folder. However, because a Workspace also defines some other settings besides the folder, you may need to create a new Workspace that will share files with another Workspace.


Main advantage of using projects (*.wsf) is that you can reference external script files from a project. Thanks to this you can split your script files into two groups; task-specific files and libraries. Script files (*.vbs, *.js, ...) placed in a Workspace with libraries option selected are easier to access when constructing a project.


Because a project (*.wsf) enables to mix scripts written in various scripting languages (such as VBScript, JScript, etc) you can select what languages you are going to use with the Workspace. This setting mainly affects file filters.

Project run

A project (*.wsf) can be executed by Windows Script Host version 5.6 or higher. Select whether you prefer window-based version (WScript.exe) or a console-based version (CScript.exe) of the host.

Script run

A script can be executed by Microsoft Script Control (embedded into the Editor) or by the Windows Script Host.

  Microsoft Script Control
(embedded in Editor)
Windows Script Host
Advantages If execution fails, either for a syntax or run-time error, Editor shows error in the Script Errors list, opens the affected script and places the cursor at the line and character of the error. WScript object is available. WScript.exe and CScript.exe are standard parts of the Windows system.
Disadvantages WScript object is not available.
Projects (.wsf) can't be executed with it.
If execution fails the line number and the char number of the error must be entered manually for the feature Find WSH Error to locate the error.

Used objects

Specify the objects you will probably need to build your project (task). The objects entered here will show up in the object browser on the left and therefore their methods and properties will be easy to insert into the script.

Editor behavior

Specify what Editor should do when a project or a script is started. By default, the GUI remains visible on the screen. However, it is also possible to minimize it or hide.

See Also
User Interface, Workspaces, Understanding Workspaces, Workspace Settings, Workspace Content, Workspace Files