Thanks, a lot, it may help.

But unfortunately, Export in case of Base64 does not work correctly, and anyway have to be fixed. Due to the specialty of Base64, a string which has to be encoded in a chunked manner, have to be devisable by 3. At the moment it reads original stream with default size of chunk, 32656 (instead of 32656\3*3=32655), so, base64 becomes incorrect, and decoded back is different from the original.

Hi Emmanuel,

This particular extension is for Visual Studio Code only, at the moment. Different IDEs I hope will come in the future. And possible for Visual Studio as well.

VSCode supports Cyrillic, so, don't see any possible issues with Hebrew.

Visual Studio Code and Visual Studio are two completely different projects. There is only one thing between them, both developed by Microsoft. Don't be confused by similar names. 

So, you should not be worried to use VSCode and Visual Studio on the same machine side by side.

Thank you guys for coming to our first webinar! Wow! I did not expect that there will be more than 80 participants! Thank you for your interest and support.
We will make more overview webinars further on. But if you want to dive deeper you can sign up for our online course!
The first 3 subscribers will get 50% off the price!!

Fill free to post any issues with VSCode-ObjectScript you faced here

Possible reasons

  • Another recommendation is to separate code and data. So, I need at least two databases, code which is always in a container, and data mounted outside.
  • Just to be consistent, some project, and namespace with the same name as the project. With only own configuration. Without anything predefined. In most cases, namespace and any related configuration, supposed to be configured for the particular project. And keeping USER as is and do not touch except for some temporary staff, like import Installer manifest and setup it.
  • One of the reasons for USER still exists, that it is kind of entrypoint, and keep it as is, will keep from anything unexpected.

Just my thoughts

Any IRIS edition includes formerly known as Ensemble feature, which is now is Interoperability (and one of the letters in IRIS).

You may get this error if you work in the namespace where Ensemble was activated. By default for USER was not activated.

When you create a new namespace Ensemble checkbox checked by default and, but you can uncheck it.

to enable namespace manually, do this command

do ##class(%EnsembleMgr).EnableNamespace("YOUR-NAMESPACE")