#VSCode

Earlier this year I announced availability of a VS Code extension for coding in ObjectScript, Embedded Python or SQL using the notebook paradigm popularized by Jupyter. Today I published a maintenance release to correct a "getting started" problem.

Here's a video of the installation steps from the extension's README:

(video superseded by an update in a later comment)

Why not try it for yourself?

The best way to list, edit, save and delete globals is using an IDE. Now, it is possible if you use VSCode. It is also possible to save globals using yaml files. Perform the following steps:

1. Get an InterSystems IRIS instance and install the application iris-global-yaml: 

zpm:USER>install iris-global-yaml

2. If you just to want an InterSystems IRIS trial for tests git clone and run on docker:

git clone https://github.com/yurimarx/iris-global-yaml.git
docker-compose up -d --build

3.

VSCode is the most used IDE in the world. It is strategic have more extensions for VSCode for InterSystems technologies to keep increasing the developer community.

My new app IRIS VSCode Global Editor is an excellent sample to learn how to create extensions to IRIS. You can check it on https://openexchange.intersystems.com/package/IRIS-Global-VSCode-Editor.

To be ready to create extensions for VSCode

From https://code.visualstudio.com/api/get-started/your-first-extension you have all steps to get ready, but I will detail here to you.

1.

Visual Studio Code releases new updates every month with new features and bug fixes, and the November 2024 release is now available. 

Hey Community,

Enjoy the new video on InterSystems Developers YouTube:

⏯ FHIR Object Model Classes in VS Code

So being forced to use VSCode out of the box for a new Community install I've hit a small problem, documentation hasn't helped and its a simple problem.

How do I enable auto complete and the property viewer in creating a new .MAC?

So I've created "test.mac" and 'assume' can't remember the method name to open a file (for example), typing

"s f=##class(%Library.File).   " in Studio would bring up the methods of %Library.File so I could click the appropriate one, VSCode does not do this (and also didn't show the classes under %Library).

Please don't reply telling me how to open a new file :-), I'm

Hi All,

I'm trying to connect to an IRIS instance using VSCode, the problem is, there are 2 IRIS instances installed on this server, published by the same hostname using https (port 443) under 2 different subfolders (e.g., iris.demo.com/base & iris.demo.com/test).

When connecting via studio, I was able to connect by using the hostname (e.g., iris.demo.com) and specifying the super server port, while when connecting through VSCode, when specifying the web server port 443, the connection is always defaulted to one of the instance.

Is there any way we can specify the instance in VSCode?

Many thanks!

We've just made a change to Server Manager with the aim of it coping better when a stored password is no longer valid, for example because it has been changed.

We plan to include this in the next published version (no release date yet set), but if you'd like early access please download the v3.6.3-beta.3 VSIX and install it, for example by dragging it from your file explorer onto the Extensions view in VS Code.

If you encounter problems with this beta you can easily revert to the most recent published version (3.6.2) by means of the "Install Specific Version..." option on the gearwheel of the

Hello,

Since version 1.93 of VS Code, the “import and compile” process has been very slow (more than an hour).
Have you encountered this issue and do you know how to resolve it?

Thank you,

Maxime

This is a consequence of work being done by the VS Code team to improve Find in Explorer.

Symptoms without proposed APIs:

Note the continual clock badge and progress bar.

With proposed APIs enabled you will require v2.12.9-beta.4 or later, otherwise the find runs but returns no results.

See https://github.com/intersystems-community/vscode-objectscript/issues/14… for more information.

Visual Studio Code releases new updates every month with new features and bug fixes, and the September 2024 release is now available. 

Version 1.94 now includes: 

• Find in Explorer - Quickly find files in the Explorer view with the improved Find control. As a consequence of this, the Explorer's Find widget on server-side folders requires v2.12.9-beta.4 or later with Proposed APIs enabled. Read more in this Developer Community post. 
• Source Control Graph - More filtering options and interactivity in the Source Control Graph.
• Python test coverage - Run Python tests with coverage and get rich

I have three different methods for exporting classes and projects as XML files, but each one produces slightly different output:

1. Studio (what I currently use for exporting): I export as a project (with the 'only project' option disabled). This generates all classes and the project in a single XML file.
2. VS Code: This method only exports the classes, and it doesn't include the project in the XML file.
3. Console export using %SYSTEM.OBJ.Export: I used the following command to attempt the same export as Studio: do ##class(%SYSTEM.OBJ).Export("MyProject.Prj, MyProject.*.cls",

On 2024-08-29, the team released Language Server v2.6.0, which includes more improvements for code completion (aka intellisense). That means that #dim, while still useful, is hardly necessary anymore. That's a good thing in my opinion.

This post from last year (Intellisense and code completion in VS code objectscript) talked about using #dim for code completion for OREFs. #dim has always been useful for both Studio and VS Code.But last year, VS Code ObjectScript was slightly behind Studio in this area, and #dim helped bridge that gap.But now, VS Code has surpassed Studio.

Please allow me to introduce you to a new way of interacting with IPM (InterSystems Package Manager), also known as ZPM,directly from inside Visual Studio Code.

First, install into VS Code the free InterSystems Package Manager extension, published to Marketplace by George James Software. A quick way is to use the search field in VS Code's Extensions view and look for 'ipm zpm' (without the quotes). Alternatively browse to https://marketplace.visualstudio.com/items?itemName=georgejames.iris-pa…

Here's a short video showing the extension in action.

If you like it please vote for it in

hi everyone,

I'm trying to make some use of AI to help with coding. To achieve this I've moved to VS Code linking to a cache instance, and installed the "Cody" extension from Sourcegraph that talks to Claude Sonnet.

In theory Cody can view, and send to the AI, the file I'm currently editing. However, it does not seem to "see" Cache server items, and only works for stuff in ordinary files that I have open. Is this an issue with "isfs" ("InterSystems File Service" that implements the "filesystem provider API" )? Is anyone else using Cody or any other AI extension successfully?

Thanks,

Mike

Hello,

I'm trying to debug objectscript ClassMethods in VSCode, but nothing happens when clicking the Debug button over the ClassMethod.

This was working with previous versions - tested with IRIS 2020.

This is the server configuration:

"intersystems.servers": {

        "iris": {

            "webServer": {

                "scheme": "http",

                "host": "localhost",

                "port": 80

            },

            "username": "superuser"

        }

    },

Editing and compiling ObjectScript is working:

I checked the vscode devtools and saw an error every

If you are using the client-side development paradigm (i.e. editing code in local files that get imported and compiled onto the IRIS server your `objectscript.conn` settings point to) you can now use IPM in VS Code to manage the packages in your IRIS target by launching it from the Explorer view. Just make sure the extension you are using is at least version 1.0.4, then use this button:

Thanks to @Evgeny.Shvarovfor suggesting this enhancement, which is particularly useful when using Docker.

See the new team members in action:

Try them online for yourself:

https://gitpod.io#snapshot/b31bdf9c-4657-402a-a2d

Get it from the Extensions view inside VS Code, or here in Marketplace.

Vote for it here in the current Developer Tools 2024 contest (voting ends: 29 Sep, 2024, 11:59:59 PM EST).

Discuss it below.

Most of all, enjoy DX Jetpack with its added booster rockets!

If you use VS Code and ZPM / IPM, and would like a GUI-type alternative to the CLI of the latter, please upvote https://ideas.intersystems.com/ideas/DPI-I-602

Suggestions about how you think this new UX should look and behave are welcome, so feel free to add your comments to the idea.

Hello,

Since version 2.12.6 of "Intersystems ObjectScript" extension in VS Code, the compile process force the EOF automatically to LF.
Have you encountered this issue and do you know how to resolve it?

Thank you,

Maxime

Visual Studio Code releases new updates every month with new features and bug fixes, and the August 2024 release is now available. 

Version 1.93 includes: 

• Profiles editor - Switch and manage your profiles from a single place.
• Django unit test support - Discover and run Django unit tests from the Test Explorer.
• IntelliSense on vscode.dev - Boost your JS & TS coding in vscode.dev with IntelliSense.
• Notebook diff viewer - Efficiently review changes in notebooks by collapsing unchanged cells.
• Resize columns via the keyboard - Resizing table columns in VS Code more accessible via keyboard.
• S

during an upgrade, a customer wants to load custom schemas in a particular order.
For this, they renamed a file EPIC_MDM.HL7 to 1EPIC_MDM.HL7
Upon importing this file into their server using VSCode, the custom schema was renamed to 1EPIC_MDM.HL7 inside the <Category>
This is impacting the upgrade and they are looking for a way to import a custom schema without renaming the schema itself.

For those of you who still use the Studio IDE for ObjectScript programming and are going through the process of migrating to VS Code, did you know there's a section in the VS Code documentation just for you? Have a look at the Migrating from Studio chapter. It covers:

• Server-side editing and source control
• Studio projects
• Importing server definitions from the Windows Registry
• Loading Studio snippets and syntax colors

And now there's a new section, Keyboard Shortcuts, that shows you the VS Code equivalent for shortcuts you may be used to, so your hands never have to leave the keyboard.

Instead of building a BP to execute stored procedures just to insert the data, I figured I would give Linked Stored Procedures a try since all I need to do is insert the data. I have proved in our MS SQL Development environment that it is possible, so I through I could just repoint the Linked Stored Procedure 

set hdbc=$$GetJConnection^%apiGTW("xxxxx")

to the test environment. But when I made the changed in VSCode and compiled the Stored Procedure disappeared from the SQL view in the Management Portal.

So can we not simply update the connection string to point to a different MS SQL Connection?

Is there a wizard to override pieces of class (parameters, properties, methods, etc.) like there is in Studio? I can't find this functionality anywhere. If it's not there, it's certainly a piece I'll sorely miss as we transition to VS Code.

Is CR/LF changes to DTL files edited/committed to git via VS Code a known issue?

We had an issue with exporting files from one server and importing on another, using XML code exported from Studio: ERROR #6301: SAX XML Parser Error. Turns out that issue was down to CR/LF changes made when transferring the XML from one server to the other.

Now we are getting the same error only with DTL files when (1) creating DTL on Management Portal, then (2) exporting via VS Code ObjectScript extension, (3) committing to git (GitLab, self-hosted instance, if it matters), and then (4) subsequently cloning from

What is wrong in this snippet??

Its an iris lab so nothing so personal that someone can't use it

{

    "workbench.colorTheme": "InterSystems Default Dark Modern",

    "intersystems.servers": {        

        "irislab": {

            "webServer": {

                "scheme": "https",

                "host": "35.188.112.210",

                "port": 29363

            },

            "username": "tech",

            "password": "demo"

        }

    },

    "objectscript.conn": {

        "server": "irislab",

        "ns": "USER", // Add your namespace here (e.g., USER)

        "active": true

    }

}

Hello,

I have installed the latest version of IRIS (without a web server) to replace my community version with a embeded web server. 
I tried to connect Visual Studio Code to my namespace, but I am unable to do so. I keep receiving the message "Not found." 
Here is my configuration:

"pc-david": {
    "webServer": {
        "scheme": "http",
        "host": "localhost",
        "port": 80
    },
    "description": "pc-david",
    "username": "_SYSTEM"
}

When I modify the host and port, I can successfully connect to other remote databases (Cache 2018 or IRIS). 
However, I cannot connect to the one on my