#VSCode

I am going to share some of the things I find very useful about VS Code, after many years developing in Studio.

The first and obvious thing to me is the fact that it does not crash in the middle of development when it disconnects from the network for any reason, forcing you to restart Studio and deal with the risk of losing valuable code. I also find VS Code a lot quicker than Studio, and the user interface far better with so many ways to customise it to your liking.

In France we use farm animal names for our dev and test environments.

If you're running IRIS behind IIS and get this error when trying to open the Lite Terminal in the vscode-objectscript extension:

WebSocket error: Error: Unexpected server response: 101

check your IRIS Web Gateway log. If you see:

level=SEVERE event=WebGateway.WebSocketError
This Web Server does not support WebSockets

the fix is to enable the WebSocket Protocol IIS feature, which is not installed by default.

One the main differences is the plugin system. Because in VS Code, everything is built around extensions. For example, for InterSystems development, you have the "InterSystems ObjectScript Extension Pack" that includes the essential tools. With this plugin you can connect to InterSystems servers, browse code, edit classes, compile, and work with ObjectScript directly from VS Code.

And it's not just for ObjectScript. VS Code also supports Git, Docker, REST clients, YAML, JSON, Python, and many other technologies.

Hello everyone,

For the past few days, I have been experiencing a strange issue with the InterSystems Server Manager in VS Code (v.2.8.3).

Sometimes, while working on a .cls class in client-side mode (editing files locally and pushing them to the server through the VS Code extension), the extension unexpectedly starts recompiling the same class multiple times. The compilation itself completes successfully, but as soon as it finishes, another compilation of the same class is automatically triggered.

Welcome to the monthly recap of updates and releases to VS Code and InterSystems-related extensions relevant to IRIS developers. 

Don’t forget, if you’re migrating from InterSystems Studio to VS Code, or want to deepen your knowledge, check out the VS Code training courses from George James Software: georgejames.com/vscode-training. 

This recap covers the four VS Code releases in May: v1.119, v1.120, v1.121, and v1.122.

Editor and navigation

• Quieter inline suggestions (v1.

Hello everyone, I am working with the VSCode extension by connecting to clients' IRIS servers remotely with my personal user (pdileo). However, one of the development environments was recently updated and my user was created for the second time with a different password.

I noticed that the VSCode extension no longer allows me to log in because the password has been changed, without asking me for a new one, only showing the 401 AxiosError.

IRIS is installed and running in an Ubuntu VM.

Visual Studio Code is being used in the host Windows OS and is connected to the IRIS server.

When attempting to execute commands with sudo from the InterSystems Lite Terminal in VSCode using $ZF(-100), error code 127 is returned.

I tried configuring Ubuntu to avoid password prompts by adding the following line to /etc/sudoers.tmp:

ALL=(ALL) NOPASSWD: ALL

However, the above configuration did not work.

Is there a way to execute sudo commands from InterSystems IRIS Production ObjectScript code in Ubuntu?

I recently started using Cursor/VSCode with an IRIS container for development rather than Studio/Terminal.  
I've noticed that whenever I use %G (so basically all the time), when I exit %G, the terminal window simply closes, rather than returning me to my usual namespace prompt.  
%G also does not retain the command stack like it does in old school terminal, so I'm forced to constantly retype every global reference.  
Anyone figured out a solution to this?  It's a relatively minor problem in the grand scheme of things, but a time consuming and irritating one.  
 

Introduction

Today, coding assistants like Claude, GitHub Copilot and Cursor have transformed the way developers write code. However, these tools are limited by being isolated from the systems and data sources that developers work with daily. This limitation can be overcome through the Model Context Protocol (MCP), an open standard designed to connect AI assistants to external data sources and tools in a secure and standardized way.

In this review article, we'll explore the current state-of-the-art regarding the MCP within the InterSystems ecosystem.

1. VS Code version 1.60.0 and above

2. install below 3 extensions

   

3. Ctrl + Shift + P show all commands

4. InterSystems: Connect to Server

5. input connection details 

   IP：localhost

        Port: 52773

       choose global & http connection method

       Input username and password of Intersystems management portal

       screenshot for success connection:

Introduction

In healthcare interoperability environments, InterSystems Health Connect typically contains critical components such as productions, business processes, operations, services, utility classes, routines, and other ObjectScript artifacts. Traditionally, many deployments of these components have been done manually, by copying classes, importing XML, or using administrative tools from the management portal.

Since our previous announcement, we have introduced several incremental improvements to the client‑side editing experience in VS Code. These updates focus on preserving developer‑authored formatting when synchronizing with the server.

What Changed

Client‑side *.cls files previously lost certain formatting details during compilation, including keyword casing (e.g., classmethod → ClassMethod), normalization of blank lines between class members, and removal of line breaks within parameter lists.

Over the past year there have been a few DC articles offering MCP servers designed to connect to IRIS and help the AI features of VS Code and its cousins do a better job. For example:

• Hey chat, what's up with my Interoperability by @Dmitry Maslennikov 
• No-Hallucinate MCP: Real-time Routine Context for ObjectScript by @Jinyao 
• iris-mcp-atelier introduced by @Ernest Salas in his comment on the Claude Code vs ISFS. Has anyone cracked how to get one to see the other? post by @MarkCharlton.

Hi everyone,

I was wondering if it is possible to use the InterSystems Server VSCode Extension to work in client side mode but importing locally the content of a project without having to choose the files manually.

It would be awesome to have all project-related assets synchronized in one go. Relying on InterSystems Projects (.prj files) would be convenient for several reasons:

1. Projects bundle different file types (CLS, MAC, INT, CSP). Importing the project as a whole is much more efficient than picking individual files piece by piece.

i want to debug classmethod in vs code,bu it get error !

If you have ever dug through a large IRIS namespace looking for where a particular string, method call, or pattern was used, you know the pain: there was no built-in way to do a grep-style search across your server-side ObjectScript code from VS Code — at least not without jumping through some hoops.

That is what ObjectScript Search fixes.

Try it today with a simple install from the VS Code Marketplace. If you don't like it, uninstalling is just as easy. But I think you will like it — it is a huge quality-of-life improvement for anyone doing ObjectScript development in VS Code.

Welcome to the monthly recap of updates and releases to VS Code and InterSystems-related extensions relevant to IRIS developers. 

If you're migrating from InterSystems Studio to VS Code, or want to deepen your knowledge check out the VS Code training courses from George James Software: georgejames.com/vscode-training.

VS Code version 1.110
Kitty graphics protocol in the Terminal - The integrated terminal now supports the Kitty graphics protocol, allowing for high-fidelity image rendering directly in the terminal pane.

When using VS code with multiple workspaces it requests "The extension 'InterSystems ObjectScript' wants to sign in using InterSystems Server Credentials. 

Other than having multiple workspaces per environemnt (which never really works for me in principle as i end up code comparing in one manner or another) is there a way to only have intersystems log in to VS code whenever you open an actual workspace itself i.e. click on dev not on loading vscode. 

This would also get around errors of "unauthenticated access rejected by" errors as VS code tries to log in without the password first.