The InterSystems® extensions enable you to use VS Code to connect to an InterSystems IRIS® server and develop code in ObjectScript. This document covers issues specific to those extensions and working with ObjectScript and an InterSystems IRIS server. The Visual Studio Code DocumentationOpens in a new tab is an excellent resource on VS Code, so it is a good idea to be familiar with it in addition this document.
Development in ObjectScript involves both your local client machine, and an InterSystems IRIS server. Because both resources are required, the available workflows are different from that typical for many languages:
With client-side editing, source code files are edited on the client, and saved to the local disk where they can be managed with a version control system. In addition, source files are imported into an InterSystems IRIS server, where they can be compiled, run, and debugged.
With server-side editing, source code files can be edited directly on the InterSystems IRIS server. VS Code’s multi-root workspace featureOpens in a new tab allows you to edit source files stored within different namespaces and even different servers simultaneously. Source files can then be compiled, run, and debugged on their respective servers.
Source code files are edited on the client, and saved to the local disk where they can be managed with a Version Control System. In addition, source files are exported to an InterSystems IRIS server, where they can be compiled, run, and debugged.
For existing customers, the InterSystems ObjectScript extension supports Studio extensions, as provided by %Studio.Extension.Base. If you rely on Studio extensions such as source control hooks, you can continue to use them in VS Code. VS Code is supported by InterSystems Caché® and Ensemble 2016.2 and higher, and all versions of InterSystems IRIS.