#VSCode

In VSCode using the InterSystems extensions, I now have an almost working environment where routines can be created or modified on disk and these are pushed to the developer's IRIS instance.

One issue I'm finding whilst testing is that if I rename or delete a routine from disk, the change isn't pushed to IRIS and I can't work out how to make this happen.

We have some custom tools that do project based deployment from environment to environment. In VS Code, we're struggling to find the best way to export PRJ files that contain the contents of a project the way we were able to in Studio. We can edit existing projects, and in server side editing we can create projects, but we can't seem to extract the project files (Not the classes, the wrapper) to store in our source control solution for deployment purposes.

I have a problem. Occasionally, I am getting locked out of IRIS because of password failures. However, the failures aren't necessarily related to my password. We are using VSCode, and I have installed one or two proposed APIs for use with the software (because that's just how I am; I want to learn the new stuff).

Today, I had that problem again. The step that caused the problem was most likely when I was trying to switch the branch I was using and updating within VSCode. Let's say I was switching from branch "1A" to branch "2B". When I did this, IRIS caught two password errors:

In Studio, I had a set of nice Assist Functions to create correct code..

Do they exist in some similar way also in VSCcode ?

Same for SOAP wizard?

It's not too late to strap into the DX Jetpack for VS Code, take it for a test flight, and consider voting for it.

Online demo on Gitpod is HERE.

Ignore any initial notifications about ports being opened.

The ServerDiff extension will ask for permission to reinstall itself in order to use the `quickDiff` API proposal that it relies on. Click 'Yes'.

I am trying to adjust my VSCode settings.json to make my repository to Server Side Source Control. When Adding "uri" to the settings.json to change the setting but VSCode is telling me that the Property uri is not allowed.

Why is this happening?

Hi folks!

I'm playing with Embedded python with IRIS trying to do some 'hello-world' exercises.

I'm running IRIS in container and have the following python code:

When using VS Code for Objectscript, is there a way to directly open % classes, like %Library.String, without needing to search for a property of that type and right clicking->"Go to Definition"?

I know it is possible to use "system=1" in the workspace uri definition to see all the % classes, but that tends to clog up the left side viewer with many extra directories. There is also the option in the settings to selectively hide some by defining files.exclude, but it seems fairly complicated to set up a filter for exactly the relevant directories.

Hi folks!

We have a bunch of templates on OEX that provide a handy foundation for building a particular application with IRIS. And the basic principle of each and every template is that we take vanilla IRIS images, load code, and files into the image using Dockerfile, and create a new docker image as a solution. And then we develop running this image and rebuilding it when returning to development.

Some developers ask me why we need to build the docker image to work with the code. Indeed, if at the end of the day I need to develop a ZPM package and not a docker image why don't run the vanilla image and load the code and everything in it?

The problem I have with the building image approach is that often I can wait a lot to build an image and it fails on some Objectscript problem in the source that I cannot fix as the image is not building. and

Any thoughts? How do you develop with docker?

I am writing documentation in VS Code, using markdown, and am including some COS snippets in it, e.g.:

```objectscript
[Some COS snippet]
```

The IRIS language server (etc.) is enabled, and classes in the repository this documentation is in, are syntax highlighted properly. However, the code fragment in the documentation isn't. Syntax highlighting for e.g. XML does work.

Am I doing something wrong, or is this not supported?

Is there a straightforward workflow in VS Code for moving a class from one namespace to another on the same server? With Caché/IRIS Studio, it was a (sort of) simple export/change namespace in file menu/import operation. But in VS Code it's not obvious (to me, at least).

I can add multiple namespaces to a workspace, but when using isfs:// paths I see only a "Download" option and no "Upload" or "Import/Compile." When I'm navigating the local file tree, I see Import options, but no way to select the namespace into which I want to import.

Hi,

I've started active use ISC VS Code extensions about a half year ago, seem to be used to use, and started to enjoy them :)

The documentation promises the

Hi all,

I wonder how to sync my server code to my local code using Visual Studio Code.

Previously, using Atelier, you could open a view of server and can copy the code to the current project, also if I change a BP, I could sync the code because I had a signal that It's warning me that there was a change and it needs to be updated.

I thing i shouls opening the ObjectScript: Explorer and select the code directaly, and right click -> Import and compile current file (Ctrl + F7)

If I use this command, the ouptut window shows:

Hi folks!

Want to share a lifehack with you on ObjectScript highlighiting withing VSCode for script files.

Script files are just files with lines of ObjectScript that we feed anywhere, e.g. into IRIS during Docker baking procedure.

Typical usecase - here is the Scriptfile

here is the Dockerfile where we feed it.

And here is how it looks like usually in VSCode:

Coudl be more beautiful, right?