Yes, I recommend you migrate away from using XML exports of class definitions.

The technique I have seen used is to run a JS timer which will run for, say, 120 seconds less than the session timeout. Restart the timer each time something happens that will cause the server-side session timeout to restart. When the JS timer expires, display the "2 minutes before timeout" message, perhaps with a countdown run by another 1-second JS timer.

Did you take a look at the Snippets provided by the extension?

Implementation details are at https://github.com/intersystems-community/vscode-objectscript/blob/maste... for class snippets. 

You need to use the Sorts After operator ]] to do this.

See https://docs.intersystems.com/iris20223/csp/docbook/Doc.View.cls?KEY=GCO...

I've recently been using codetidy as an example codebase. See https://community.intersystems.com/post/gj-codespex-now-supports-exclusions

In VS Code the "editor.insertSpaces" boolean setting governs whether or not pressing Tab will insert a tab character or a number of space characters (specified in the "editor.tabSize" setting).

"editor.insertSpaces" is one of the settings which can be specified per-language. The command "Preferences: Configure Language Specific Settings..." gives you a language picker, then seeds the Settings Editor filter so you can easily set a language-specific value. Below is a screenshot showing how I can make the Tab key enter the tab character when in a document set to the objectscript-class language.

You make a good point about how Python-coded methods must be space-indented. VS Code can't help you with this, as it sees the entire .cls document as being objectscript-class language. So I suggest you leave "editor.insertSpaces" at its default (checked / true). The ObjectScript-coded methods won't mind being space-indented.

Please see https://community.intersystems.com/post/unc-path-not-recognized#comment-... and the post it refers to. 

You could use the technique I described in https://community.intersystems.com/post/class-projections-and-projection...

my guess that if we specify port 57772 as the default port in the web server which I'm assuming that would be Apache , we don't have to specify the port in our url

No, if the web server (Apache or any other server) is listening on any port other than 80 (for http protocol) or 443 (for https protocol) your URL needs to tell the client app (e.g. your web browser) to connect to a port that is not the standard one for the specified protocol.

Also, server-side editing mode can deal with CSPs. See https://intersystems-community.github.io/vscode-objectscript/serverside/..., or if you use Server Manager's "pencil" button alongside a namespace in order to create your isfs workspace, hold the Alt key down when clicking it and you'll get a workspace folder which shows you the CSP app files.

Mark, if you are using the server-side editing paradigm, which matches what you're used to with Studio, make sure you follow the instructions in the "Enable Proposed APIs" section of the extension's README (also available here). Until you have done this the Ctrl/Cmd+P technique mentioned by Dmitry won't find anything when you are working server-side.

Does WinSQL use ODBC? If so, does the ODBC driver need to be upgraded?

Perhaps worth noting that you can combine Joel's "#dim" and "set" lines into a single one if you wish. See https://docs.intersystems.com/iris20222/csp/docbook/DocBook.UI.Page.cls?...

Do things improve if you rewrite your first line to be this?

   #dim tObservation as HS.SDA3.Observation = ##class(HS.SDA3.Observation).%New()

In the Extensions view if you search for "intersystems" does it offer you the option of installing the extensions into your container? Or have you already done that?

Here's what I recommend (assumes you are using Server Manager extension as well; can be done without it but you'll have to edit JSON in a file):

1. In Server Manager's tree, expand the namespaces of your server.
2. Clock the "eye" icon on the %SYS row. This will add another root folder to your VS Code workspace. The folder uses the `isfs-readonly` scheme to access the namespace directly.
3. In VS Code's Explorer (not ObjectScript Explorer), expand that folder and drill down to find the class you want.

Assuming you want to use this multi-root workspace again, use "Save Workspace As..." from the File menu. If you don't, you'll be prompted when you exit VS Code and given a choice of saving or discarding.

Documentation at https://intersystems-community.github.io/vscode-objectscript/configurati... has now been updated to include this information.

Please open an issue at https://github.com/intersystems-community/vscode-objectscript/issues

Screenshots can be pasted from clipboard direct into GitHub.

Thanks.

Turns out it wasn't hard to add this. Download and install 1.8.2-beta.2 if you want to try it out.

Only the editable file gets coloured, not the preview. It may be possible to address that, but would require more work than I have time for at the moment.

I haven't seen this problem.

The GitHub source of this method doesn't seem to check the status of its ParseStream call before trying to read the stream:

Maybe your upgrade procedure went wrong. I suggest you download the XML distribution and import it again.