Announcement
John Murray · Apr 16

Announcing Server Manager 2.0 for Visual Studio Code

I'm pleased to announce a major release of the InterSystems Server Manager extension. It has gained a UI!

Read more at Open Exchange.

Right now version 2.0 is like an aircraft at the start of the runway (remember those days before COVID-19?), waiting for the control tower to give final clearance. Will you be an early adopter, downloading the VSIX from GitHub, installing it into your VS Code, and posting back here to confirm that we haven't left anything critical behind at the gate? Then I'll push the throttles forward, publish to Marketplace, and we'll all be on our way.

Server Manager 2.0 is my entry for the current contest. If you like it maybe you'll vote for me it. wink

100
2 2 6 343
Log in or sign up to continue

Maintenance release 2.0.2 is now on Marketplace, so your VS Code can easily update to it. Here's what it contains:

  • Support Alt / Option modifier on Edit and View buttons to add workspace folder for server-side web application files.
  • Add newly defined server to the 'Recent' list.
  • Handle repeated use of the same Edit or View button better.
  • Notify user if ObjectScript extension is missing.
  • Add more information to README.

Thanks for all the votes this entry has received so far.

I have been using VS Code with client-side editing exclusively. Now I'm playing with server-side editing, and I'm hoping that @John Murray or someone else can clear up my confusion about something. Before Server Manager had a GUI, my (possibly incorrect) understanding of server-side editing was that there were two ways to configure it:

  • The preferred way was to use the isfs "technique" as described in the documentation
  • Just click "Choose Server and Namespace" without creating a Workspace (no local folder)

It now appears that clicking "Choose Server and Namespace" automatically uses the isfs technique. Now I'm wondering:

  • Did the behavior of "Choose Server and Namespace" actually change? I'm kind of hoping that it didn't change, but if it did...
  • What's the difference (if any) between the two techniques for server-side editing, and is there any reason to still use the non-isfs approach, and if so, how would I configure that?

No, nothing changed. When the "Choose Server and Namespace" button appears in the Explorer view (the VS Code Explorer, not to be confused with the ObjectScript Explorer) it's because you don't have a workspace open.

After clicking that and working through the input prompts you now have an untitled (i.e. unsaved) workspace consisting of a single isfs-type root folder.

Thanks! One more followup question: Does all of the above now supersede the following setting?

That setting affects how the ObjectScript Explorer behaves. That's the tree you get if there's an InterSystems logo on your Activity Bar and you click on it. It's the tree whose primary purpose is to let you export server code into files on your workstation that you then edit locally, probably add to a Git repo, and import to your server to run and debug it.

When you select a class or routine in that tree, and it only exists on the server (i.e. it isn't one that you have already exported locally), then the above setting dictates whether the code is opened read-only or editable.