We just published 3.0.2. If you already installed 3.0.0 your VSCode extension should upgrade automatically next time VSCode checks for extension updates. Or you can trigger that from the "..." menu on the Extensions viewlet. For best effect you should also upgrade the server-side part wherever you've previously been connecting from 3.0.0.

Changes in 3.0.2:

  • Upgrade embedded Deltanji to version 7.0.
  • Support networked Deltanji Enterprise edition environments.
  • Automatically add embedded Deltanji aliases for new usernames.
  • Report permission problems at connection time.
  • Support prompting for username at connect time.
  • Remove 'Preview' flag from Marketplace entry.
  • Improve documentation.

Serenji is also listed on Open Exchange.

We have no current plans for implementing Serenji for VS. The architecture of VS is significantly different from that of VSCode.

I notice that your mappings get code from ENSLIB

My use-case is a bit different.

Can you create a new database and namespace pair called XYZ and then define a %ALL mapping so that the globals ^XYZ and the routines XYZ* and the package XYZ get fetched from your XYZ namespace from all other namespaces, e.g. USER ?

I'd expect mappings to ENSLIB to work, otherwise the "Ensemble" features of IRIS would be broken in Community Edition.

It seems to me that those are allowed but mappings we define to our own databases get ignored.

I was able to create the mappings, but they don't seem to work for me. Not even after an IRIS restart.

I'm using the %ALL pseudo-namespace.

Expanding on what Evgeny wrote, the new Serenji extension from us at George James Software gives you an experience that's most similar to what you're used to with InterSystems Studio. It connects you directly to the namespaces of your servers, even if they're running versions that are too old to support the Atelier REST APIs which other VSCode extensions depend on.

Plus, Serenji offers debugging.

To clarify Robert's answer, on InterSystems IRIS the database is called IRISLIB, and on Caché, Ensemble etc it is called CACHELIB.

But rather than having to reload your own non-%Z/%z routines after every upgrade you could create a dedicated database for those routines and then use %ALL-type mapping to make the routines available in all of your namespaces.

More info:

@oliver russell I think you are confusing the name of an InterSystems product (Caché) with the term 'cache'. Easy mistake to make, ever since InterSystems released Caché a couple of decades ago.