InterSystems ObjectScript extension for VS Code
Note: The best way to install and use this extension is by installing the InterSystems ObjectScript Extension Pack and following the documentation here.
InterSystems® ObjectScript language support for Visual Studio Code, from the InterSystems Developer Community.
InterSystems ObjectScript code highlighting support.
Debugging ObjectScript code.
Intellisense support for commands, system functions, and class members.
Export of existing server sources into a working folder:
- open Command Palette (F1 or ⌘/Ctrl+Shift+P)
- start typing 'ObjectScript'
ObjectScript: Export Code from Server
- press Enter
Save and compile a class:
- press ⌘/Ctrl+F7
- or, select
ObjectScript: Import and Compile Current File from Command Palette
Direct access to edit or view server code in the VS Code Explorer via
isfs-readonly FileSystemProviders (e.g. using a multi-root workspace). Server-side source control is respected.
Server Explorer view (ObjectScript: Explorer) with ability to export items to your working folder.
Integration with with InterSystems Server Manager for secure storage of connection passwords.
Install Visual Studio Code first.
Then to get a set of extensions that collaborate to bring you a great ObjectScript development experience, install the InterSystems ObjectScript Extension Pack.
When you install an extension pack VS Code installs any of its members that you don't already have. Then if you ever need to switch off all of those extensions (for example, in a VS Code workspace on a non-ObjectScript project) simply disable the extension pack at the desired level. Member extensions can still be managed individually.
Open VS Code. Go to Extensions view (⌘/Ctrl+Shift+X), use the search string @id:intersystems-community.objectscript-pack and install it.
Enable Proposed APIs
This extension is able to to take advantage of some VS Code APIs that have not yet been finalized.
The additional features (and the APIs used) are:
To unlock these features (optional):
Download and install a beta version from GitHub. This is necessary because Marketplace does not allow publication of extensions that use proposed APIs.
- Go to https://github.com/intersystems-community/vscode-objectscript/releases
- Locate the beta immediately above the release you installed from Marketplace. For instance, if you installed
2.0.0, look for
2.0.1-beta.1. This will be functionally identical to the Marketplace version apart from being able to use proposed APIs.
- Download the VSIX file (for example
vscode-objectscript-2.0.1-beta.1.vsix) and install it. One way to install a VSIX is to drag it from your download folder and drop it onto the list of extensions in the Extensions view of VS Code.
From Command Palette choose
Preferences: Configure Runtime Arguments.
In the argv.json file that opens, add this line (required for both Stable and Insiders versions of VS Code):
- Exit VS Code and relaunch it.
- Verify that the ObjectScript channel of the Output panel reports this:
intersystems-community.vscode-objectscript version X.Y.Z-beta.1 activating with proposed APIs available.
After a subsequent update of the extension from Marketplace you will only have to download and install the new
vscode-objectscript-X.Y.Z-beta.1 VSIX. None of the other steps above are needed again.
Configure a Connection
To be able to use many features you first need to configure the connection to your IRIS/Caché/Ensemble server(s) in your VS Code settings. If you are unfamiliar with how settings work and how they are edited, use that link.
We recommend you define server connections in the
intersystems.servers object whose structure is defined by the InterSystems Server Manager helper extension.
Install that extension and consult its documentation about its UI and commands for easy setup of connections, plus assistance when editing the JSON definition directly.
For more tips about the
intersystems.servers object, see the Notes section below.
A simple workspace -- a local working folder in which you edit InterSystems source files and manage them using client-side source control (e.g. Git) -- will use the
objectscript.conn settings object to import locally-edited code into a namespace on a server, compile it there and run/debug it, and also for initial export of an existing codebase (optional). This settings object is usually defined in Workspace Settings, for example in the
.vscode/settings.json file of your working folder.
A quick way to add
objectscript.conn to a new working folder is:
- Open the folder in VS Code.
- Use the InterSystems icon on the activity bar to switch to ObjectScript Explorer view.
- Click the 'Choose Server and Namespace' button.
- Respond to the sequence of quickpicks. You can also define a new server at the start of this sequence by using the '+' button.
For more about
objectscript.conn see the Notes section below.
To edit code directly in one or more namespaces on one or more servers (local or remote) we recommend creating a workspace definition file (for example XYZ.code-workspace) where you specify one or more root folders that directly access namespaces via the
isfs-readonly URI schemes. The only difference between these two schemes is that any file opened from a folder using the
isfs-readonly scheme will be set as read-only in VS Code and thus protected against being changed.
- Start VS Code.
- If your last-used folder opens, use 'Close Folder' on the 'File' menu ('Code' menu on macOS). Or if what opened was your last-used workspace, use 'Close Workspace'.
- On VS Code's Explorer view (⌘/Ctrl+Shift+E), click the 'Manage Servers' button which is contributed by the Server Manager extension.
- Find your target server in the tree, or use the '+' button to add a new server.
- Expand the server and its 'Namespaces' folder, then click on the 'pencil' icon for editing access to the namespace or the 'eye' icon for viewing access. If you want to work with web application files rather than classes and routines, hold down the Alt/Option key when clicking the button.
- Use 'Save Workspace As...' to store your workspace definition in a file with a
For more about
isfs-readonly folder specifications see the Notes section below.
Connection-related output appears in the 'Output' view while switched to the 'ObjectScript' channel using the drop-down menu on the view titlebar.
/api/atelier/ web application used by this extension usually requires the authenticated user to have Use permission on the %Development resource (read more). One way is to assign the %Developer role to the user.
If you are getting
ERROR # 5540: SQLCODE: -99 Message: User xxx is not privileged for the operation when you try to get or refresh lists of classes, routines or includes, then grant user xxx (or a SQL role they hold) Execute permission for the following SQL Procedure in the target namespace.
GRANT EXECUTE ON %Library.RoutineMgr_StudioOpenDialog TO xxx
This settings object is useful for both client-side and server-side development.
- An example server definition named 'local':
"description": "My local IRIS",
By defining connections in your User Settings they become available for use by any workspace you open in VS Code. Alternatively, define them in workspace-specific settings.
username property is optional. If omitted it will be prompted for when connecting, then cached for the session.
Setting a plaintext value for the
password property is not recommended. Instead, install the InterSystems Server Manager extension and use that to store your password securely.
If no password has been set or stored it will be prompted for when connecting, then cached for the session.
This settings object is primarily relevant when doing client-side development.
- We recommend that
objectscript.conn uses its
server property to point to an entry in
intersystems.servers. For example:
ns property defines which server namespace you will work with.
server property is set, any
password properties of
objectscript.conn are ignored. Instead these values come from the
isfs-readonly workspace folders
Server-side development is best done using
isfs folders. The read-only variant
isfs-readonly is also useful when doing client-side development, since it enables server-side searching of your codebase.
To modify how your folder behaves, edit the JSON of your workspace definition (XYZ.code-workspace file). Get there by using the 'Edit Settings' option from the context menu of Server Manager's 'Servers' view, or by running the 'Preferences: Open Workspace Settings (JSON)' command from the Command Palette. Edit your
csp query parameter indicates web application files are to be shown. The uri path optionally specifies which application. The namespace suffix on the server name (preferred syntax) or the
ns query parameter (deprecated) must specify the same namespace the application is configured to use. In the following example the first folder is for the
/csp/user web application in the USER namespace of the server named 'local' and the second gives read-only access to all web applications that reside in the %SYS namespace. The second folder also uses the optional
"name": "local:%SYS web files (read-only)",
- To see only classes in the Xxx.Yyy package, format the uri like this:
- Other query parameters that can be specified include:
type=cls to show only classes, or
type=rtn to show only routines.
flat=1 to flatten the hierarchy.
generated=1 to show generated items.
system=1 to show system (%) items. Without this parameter these are only shown for the %SYS namespace.
filter=filterspec to use a filter specification formatted in the same way as used in InterSystems Studio's File Open dialog (e.g.
Support and Training
CaretDev provides commercial support services. Request a quote.
On-line course from CaretDev - Developing with VS Code ObjectScript – Easy Start.