· Jan 17

VSCode New Files

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.

The folder structure inside the repo is \appname\src\database. Directly underneath the database folder is all of our InterSystems source code. If I add a new routine to the root of the database folder called, the created routine ends up being prefixed with "src.database."

In VS Code it looks like this:

In IRIS Studio it looks like this:

I don't want new routines to live in a package within IRIS called src.database.

My workspace file looks like this:


  "folders": [
      "path": "."
  "settings": {
    "objectscript.conn": {
      "server": "iris",
      "ns": "{namespace}",
      "active": true
    "objectscript.export": {
      "folder": "src/database",
      "addCategory": false,
      "map": {},
      "atelier": true,
      "generated": false,
      "filter": "",
      "exactFilter": "",
      "category": "*",
      "noStorage": false,
      "dontExportIfNoChanges": false,
      "maxConcurrentConnections": 0,
      "mapped": true

I've tried all the things I can think of to alter the workspace settings but am totally stuck on how to make VSCode know that the database folder is the root folder. I've even had a look through the github repos to see if I can track down what is going on. I should also add that I don't want to move the workspace file to within the database folder, whilst it would resolve this issue, it introduces another issue in that the developer can't select the database folder to import and compile all contents. Has anyone else tackled this issue?

Any help would be much appreciated.

Product version: IRIS 2022.1
$ZV: IRIS for Windows (x86-64) 2022.1.4 (Build 812_0_22849) Wed Nov 8 2023 17:54:43 EST
Discussion (9)4
Log in or sign up to continue

I just created a code-workspace file using your example above and I couldn't reproduce this is it possible that there's a .vscode/settings.json inside the "." folder that contains different objectscript.export settings? If so, those will take precedence. Folder-specific settings take precedence over workspace-specific settings, and workspace-specific take precdence over user-specific.