In VS Code using the InterSystems ObjectScript extensions, I'd like the indentation applied to match that of IRIS Studio. Specifically for comments and dot syntax, I'd like pressing enter (carriage return) to preserve the current dot depth and same comment beginning.

In IRIS Studio after changing the indentation settings to custom using " \t.#/;" without quotes (note the leading space), the behaviour looks like this:

And after pressing enter the leading comment is preserved:

For dot indented code:

After pressing enter the dot depth is preserved:

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.

The company I work for have a repository for one of our products which already contains both InterSystems and non-InterSystems source code. I'm in the process of trying to migrate us over to using VSCode to edit the InterSystems source but am stuck on some issues surrounding the files on disk and the routines in the IRIS instance.

When using VS Code to develop with Object Script, the Server Credentials prompt for connecting to the IRIS instance is happy accept a blank for UnknownUser. See screen shot:

From here VS Code happily connects to the IRIS instance using unauthenticated access. But the standard VS Code "Go To Definition" appears to do nothing. Whilst looking through the documentation I found that in the Language Server extension, there is a setting to output verbose trace details. With verbose output switched on, trying the "go to definition" of some code, the output shows this: