@Jonathan Lent 
Starting in IRIS 2020.1.2, 2021.1.1 and 2021.2 you can directly drill down into objects and see all of their properties during debugging. If a variable is an object, you will see its class name in grey next to it and an arrow to expand it like you would a folder in the VS Code file explorer view. This new feature is shown around timestamp 3:30 in this Learning Services produced video on debugging using VS Code.

@Kari Vatjus-Anttila 
Can you please download and install the version of the extension found here and check if that fixes the issue? To install it you can drag it from your downloads folder into the extensions view in your VS Code window.

@Peter Steiwer 
If you're working server-side, you can add the "generated=1" query parameter to your folder URI to see generated files: https://intersystems-community.github.io/vscode-objectscript/serverside/...

@Jeffrey Drumm 
Sorry, I assumed you were asking this in the context of CI. AFAIK the only way to do this is what I described. If you would like a way to do this using server-side editing, please file an enhancement request issue in the GitHub repo.

@Jeffrey Drumm 
VS Code isn't a CI/CD tool so it wasn't specifically designed for this but it is doable if you're working client-side. You can export files from one namespace, change the namespace in your settings.json file and then import and compile.

You should install the InterSystems ObjectScript Extension Pack to get full support for ObjectScript in VS Code. The InterSystems Language Server provides formatting support. You can view our documentation here and the Language Server README here.

Before SAM, there was no way to monitor Cache or IRIS using Prometheus out of the box. You had to implement the metrics exporter API yourself or use a community implementation like the one you linked. Since 2020.1, the /api/monitor API is provided by InterSystems out of the box. SAM uses this API to collect metrics and alerts from servers.

Yes, that's expected behavior. The vscode-objectscript extension defines the languages based on file extensions:

      {
        "id": "objectscript",
        "aliases": [
          "ObjectScript"
        ],
        "extensions": [
          ".mac",
          ".int"
        ]
      },
      {
        "id": "objectscript-class",
        "aliases": [
          "ObjectScript Class"
        ],
        "extensions": [
          ".cls"
        ]
      },
      {
        "id": "objectscript-macros",
        "aliases": [
          "ObjectScript Include"
        ],
        "extensions": [
          ".inc"
        ]
      },
      {
        "id": "objectscript-csp",
        "aliases": [
          "ObjectScript CSP"
        ],
        "extensions": [
          ".csp",
          ".csr"
        ]
      },

@Michael Lei SAM (or standalone Prometheus) can only monitor IRIS version 2020.1 or later.

@Dominic Chui Please try issue #2 again using LS version 1.1.6 and vscode-objectscript version 1.0.11. To diagnose issue #1, I'll need the text of the routine that you're seeing the "class does not exist" error in. Please submit an issue at https://github.com/intersystems/language-server/issues with a code sample.

@Peter Steiwer This is fixed in LS version 1.1.6 and vscode-objectscript version 1.0.11. When using those versions, the LS will check if you have a local copy of the file before opening the server copy. See https://github.com/intersystems/language-server/issues/45