Dmitry Maslennikov · Jun 10, 2019

VSCode-ObjectScript release 0.7.11

Hi all, I have released the latest version of VSCode extension for ObjectScript already a month ago, and finally a time for the info about this new release.

So, what's new in the release:

What's new in this version

  • added export setting "objectscript.export.addCategory" if enabled uses the previous behaviour, adds category folder to export folder, disabled by default
  • added Server actions menu, by clicking on server info from status bar. Open Management portal, Class Reference and toggle connection.
  • Class Suggestion in ##class, Extends, As, CompileAfter, DependsOn, PropertyClass
  • $SYSTEM suggestion by Classes from %SYSTEM
  • Import and compile folder or file by context menu in File Explorer
  • Server Explorer, now possible to open any other namespace
  • Macros suggestion

For details how it works now, look further.


  • Class name  suggestion after Extends keyword
  • Class name suggestion after keyword As. Should work in many cases such as with 
    • Property
    • Parameter
    • Method definition
    • and so on.
  • Macros usage suggestion name after typing triple dollar $$$
  • Special variable $SYSTEM suggestion.

Other changes

  • Import and Compile all files from the File Explorer
  • Server Explorer, view another namespace.
  • Go to System Management Portal
  • And to Class Reference.


As always fill free to fill any issues you faced when used this extension, or any new features you would like to see.

If you like my job, you can donate to me in any preferable way.

5 901
Discussion (14)4
Log in or sign up to continue


An amazing piece of work.

I tested this with a local install of IRIS:
IRIS for Windows (x86-64) 2019.1 (Build 510U) Thu Mar 14 2019 14:13:37 EDT

In Studio I created a test class in the USER namespace

I then opened VSCode, changed to the USER namespace and was able to open the test class

However when I tried to edit the code I saw: 

Not sure what's wrong here - any suggestions ?



David, thanks for the feedback.

Nothing wrong, explorer does not support editing, and opens files in read-only. You should export it to have local copy, and you'll be able to edit and compile.

But, with the next release I already have editing mode, so your way would work. But this way anyway not recommended.

Thanks for the confirmation.

I right clicked the Class in explorer (in VSCode), hit export and nothing happened.

Is it saved somewhere locally ? If so how do I define where it should save it ?


Yes, it should save it locally, if you opened VSCode with folder, so, it should be in src. And it is configurable. You should be able to find log in the Output view, where you have to select ObjectScript in drop-down. Compile logs, you will find there too.

Thanks - I see the package path created but no .cls file

Hi Dimitry,

I wanted to try VSCode. But I get no items in the Objectscript Explorer.

The connection is set and in VSCode displays ip:57772/SAMPLES/Connected in Status Bar. 

As mentioned I also added the %Developer Role for api/atelier...

Any idea what could be wrong?

Cache Version: Cache for UNIX (IBM AIX for System Power System-64) 2018.1.2

Thanks a lot


Could you please create a new issue here. I'll try to help to solve it. I don't have AIX system, but not sure if it could be a problem.

If you see something unexpected, you can try to look at Output for ObjectScript and just main Log, maybe some errors there, which may help to diagnose.

Problem solved, i did not add an folder first. 

But is there a short documentation for the development workflow?

I exported a src file. Then I can find it in my src folder an can edit it there.

Then I think I click on it and import and compile? But nothing happens.

I am sure I am doing something wrong

Thanks again,


Good to hear that you solved it. Unfortunately, development workflow guide is on the way, yet. But I'm going to do it this month.

First of all, any logging related to this extension goes to Output ObjectScript, so, you maybe can find there errors, or compile log.

Actually, it should compile class and notify about success or errors, just after change and save any class/routine.

Import and compile from explorer, good to use when you have changed many files in the sources folder, by Source Control System for example.

You can also trigger compile from command pallete and with a shortcut Cmd +F7/ Cmd + F7