So, today, I'm presenting a demo of VSCode-ObjectScript at CUG meetup here in Antwerp

Yep, it tries to open terminal automatically when docker-compose option used 

Hi Jose,

Interesting, I don't have windows, but as I can see, exit code 2, means 

The system cannot find the file specified.

That's strange when it successfully called docker-compose when looked for a port.

You can also try to open an ordinary terminal in VSCode (Menu, View->Terminal), and put full command there, to see how it works.

Thanks, for sharing this.

As an addition, if you have would like to use a different file name from default docker-compose.yml for your configuration, you can set it as well.

"objectscript.conn" :{
  "ns": "IRISAPP",
  "active": true,
  "docker-compose": {
    "service": "iris",
    "internalPort": 52773,
    "file": "docker-compose.yml"
  }
}

I'm going to Barcelona this year, catch me there if you would like to see VSCode-ObjectScript in action if you would like to discuss new features you want to see there if you face in issues. 

See you there

I'm finally going to Antwerp this year.

So, you have a chance to meet me there, to see VSCode-ObjectScript in action, get quick help with the migration process, and give your feedback.

See you there.

I've already published a beta version with support for CSP editing, It would be cool, if you could test it and give some feedback.

A FOR loop pushes a new level onto the stack. A WHILE loop does not change the stack level.  

Source

Working with stack takes time.

Embedded SQL queries, with variables, and INTO. When I would like to see query plan, I have to first clean it and replace with `?`.

Would be good, to be able to get query plans for such cases, a bit more easier.

Something like this, you can have many serverN folders, with own settings.json there, configured for any server.

{
    "folders": [
        {
            "name": "root",
            "path": ".",
        },
        {
            "name": "server1",
            "path": "server1",
        },
        {
            "uri": "isfs://server1",
            "name": "server1",
        },
        {
            "uri": "isfs://server1?ns=%25SYS",
            "name": "server1 sys",
        },
        {
            "name": "server2",
            "path": "server2",
        },
        {
            "uri": "isfs://server2",
            "name": "server2",
        },
        {
            "uri": "isfs://server2?ns=%25SYS",
            "name": "server2 sys",
        },
        {
            "name": "server3",
            "path": "server3",
        },
        {
            "uri": "isfs://server3",
            "name": "server3",
        },
        {
            "uri": "isfs://server3?ns=%25SYS",
            "name": "server3 sys",
        }
    ],
    "settings": {
        "objectscript.serverSideEditing": true
    }
}

Fixed

Could you explain a bit, how would you like to see work with CSP files? For me, when you working with own local instance, you can just open csp folder in VSCode, and edit as a usual file, InterSystems will compile it automatically with the next request. I think it would be possible to add CSP editor only as part of Server-side editing feature.

Server-side search, not yet available, because, search engine not yet publicly released. I've already implemented server-side search when server-side editing enabled, and you can test it with the latest beta version of vscode-objectscript, and only with Code-Insiders version, and with flag --enable-proposed-api daimor.vscode-objectscript

Could you add your expectations from debugging feature, as an issue here?

Only one server connection.

At the moment it is possible to have multiple folders configured for each own server, and tied up with .code-workspace file. I see you already use server-side editing, so, you can just extend your file. And the link for the info, how to configure it.

Curiously, what do you expect from XData? Could you fill the issue, so, for any other ideas as well?

When your team uses Studio with source hooks, it's even easier to move to VSCode. VSCode supports source control class hooks, and even some types of actions from menu. You can the latest beta release, to get more features.

VSCode can also be used to edit files directly on a server, almost the same way as Studio. Just at the moment it does not check any changes on the server, and uses your opened files as a source of truth.

Scott, could you give some more details about your experience with VSCode, privately directly to me or publicly here? What do you expect, and what would help you decide to use VSCode instead of Studio?