Version 3.0.3 has just been published. Main new feature is support for web app files (CSP, CSR and other text types). These appear in the tree under the package associated with the app:

Other changes:

  • Initialize standard workflow for embedded Deltanji (new installs).
  • Interoperate better with Studio locking scheme.
  • When launching debug, default namespace and program based on current document.
  • Recover from connect failure (e.g. bad password).
  • Report version mismatch between extension and server.
  • Offer to compose email requesting debug evaluation key.
  • Incorporate service stop / start into install / upgrade method.
  • Prepare for VSCode 1.34.
  • Prepare for upcoming Deltanji extension.

My guess is this is on Windows, and the Windows service that HealthShare runs as is configured to Log On As a specific Windows account. Check those credentials. Perhaps the password has been changed, or the account has expired, or been disabled. Look in the Windows event logs (probably the Application one). Another source of info is the cconsole.log file in the mgr subfolder of wherever you installed HealthShare.

Your problem doesn't seem likely to be specifically related to Cache Studio.

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.

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.

There's a section about Community Edition limitations in the document at https://irisdocs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page...

Here's a screenshot of what it currently says:

A big disappointment for me is the exclusion of namespace mapping. Those of us who create tools for the InterSystems world commonly use namespace mapping to make our tools available in the users' namespaces. See Evgeny's article here

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:

Take a look at methods in the %SYSTEM.Encryption class.

Like many of the classes in the %SYSTEM package, you can easily access its methods via $SYSTEM, e.g.

USER>d $system.Encryption.Help()
'Do $system.Encryption.Help(method)' will display a full description of an individual method.
 
Methods of the class: %SYSTEM.Encryption
 
AESCBCDecrypt(ciphertext,key,IV)
     This method performs AES decryption in Cipher Block Chained (CBC) mode.

...

Right. And this is the reason why the tool with XYZ.Classes should be installed in XYZ namespace - in this way even if I map XYZ to %All all the data persistent data for XYZ.Classes will be stored in XYZ namespace, even if I use it from USER namespace, right?

This is only true if you explicitly add a global mapping of ^XYZ.* to the XYZ database (NB, mappings point to databases, not to namespaces). If you only mapped the XYZ package to XYZ, when an instance of persistent class of that package is saved from within the USER namespaces its data will get stored in the USER database.