go to post John Murray · Apr 11, 2024 The set of snippets was recently reduced. Please see https://github.com/intersystems-community/vscode-objectscript/issues/1234 for an explanation.
go to post John Murray · Feb 9, 2024 It looks like you used VS Code to directly open the folder (C:\InterSystems\IRIS\CSP\goerke\) which your (local desktop instance) IRIS created for the /csp/goerke webapp it configured when you added a GOERKE namespace using IRIS Portal. I think this is going to get confusing for you, particularly if you try to use documentation or training material. Here's what I recommend you do: 1. Close your the folder in VS Code. 2. Copy your C:\InterSystems\IRIS\CSP\goerke into a folder where you will edit your source files, and perhaps in future source-control them with Git. For example, copy it to c:\MyProjects 3. Open the newly-created folder in VS Code (e.g. c:\MyProjects\goerke) 4. Reconfigure your /csp/goerke webapp in IRIS Portal so it points again to C:\InterSystems\IRIS\CSP\goerke 5. Delete all contents of C:\InterSystems\IRIS\CSP\goerke (files and folders), since you already have a copy of these in c:\MyProjects\goerke Now when you edit a CSP file in VS Code and save it under c:\MyProjects\goerke\src a copy of it will appear in C:\InterSystems\IRIS\CSP\goerke and the /csp/goerke webapp will use this. When you edit a CLS file in VS Code, saving this writes the class into the GOERKE namespace but doesn't create a file under C:\InterSystems\IRIS\CSP\goerke because IRIS classes live in IRIS databases, not in host OS files.
go to post John Murray · Feb 7, 2024 This exact IRIS version has a problem https://github.com/intersystems-community/vscode-objectscript/issues/1149
go to post John Murray · Jan 18, 2024 I'm guessing that Brett is testing on a non-Windows platform. By replicating Mathew's setup on Windows I can reproduce the issue. Mathew, please try using backslash in the "folder" property of your "objectscript.export" settings object: "folder": "src\\database",
go to post John Murray · Oct 20, 2023 Use this section: There's also a useful "Help" link in the upper right of that page (not shown in my screenshot above).
go to post John Murray · Oct 11, 2023 Starting with v2.10.3 of the InterSystems ObjectScript extension, if you launch the Server Actions menu (e.g. by clicking on the extension's status bar panel) you should get an option to "Open Studio Add-in...", and from there a list that includes the SOAP Wizard.
go to post John Murray · Oct 9, 2023 They are independent passwords. Changing the password for CSPSystem user in IRIS Portal doesn't affect the password you authenticate with when you access the Web Gateway Management page even though the username is the same.
go to post John Murray · Sep 27, 2023 Does it make any difference if you use the /exportselectivity=0 Export Qualifier?
go to post John Murray · Sep 12, 2023 I guess you are looking for a way to launch the XML Schema Wizard add-in that Studio offers. Try adapting the advice at https://docs.intersystems.com/components/csp/docbook/DocBook.UI.Page.cls... for adding a custom entry to the Server Actions menu. In this case the entry in the "links" object within "objectscript.conn" should be: "Open XML Schema Wizard": "${serverUrl}/isc/studio/templates/%25ZEN.Template.AddInWizard.XMLSchemaWizard.cls?$NAMESPACE=${ns}"
go to post John Murray · Sep 5, 2023 If you have a 2023.2 instance maybe try this: https://community.intersystems.com/post/there-something-similar-studio-o...
go to post John Murray · Aug 30, 2023 I recommend you contact WRC for help. They should be able to investigate this with you. Then if it looks like there's an issue with the InterSystems ObjectScript extension or the Server Manager one (or just possibly the Language Server) they can help you log it on the corresponding GitHub repository, or can do that on your behalf.
go to post John Murray · Aug 11, 2023 If you're using 2023.2 there's a built-in WebSocket Terminal feature, with a convenient way to launch these terminals from the Namespaces tree of Server Manager:
go to post John Murray · Jun 23, 2023 Did you find this when you searched for "epoch" here on DC? https://community.intersystems.com/post/how-convert-current-date-and-tim...
go to post John Murray · Jun 15, 2023 Please use Command Palette to run "Preferences: Open User Settings (JSON)", then review the contents for any syntax errors. My hunch is the file contains an invalid JSON structure, so the extension's call to update the "intersystems.servers" object in it is failing.
go to post John Murray · Jun 15, 2023 Thanks for the suggestions. The solution I came up with can be seen at https://github.com/intersystems-community/vscode-per-namespace-settings It installs a class, runs a method in it to create the web app so it uses the correct namespace, then deletes the class. Actually, it deletes a whole package which I named %Z.IPM.Bootstraps with the idea that this could be by convention a package reserved for exactly this purpose. I had to devise a little hack to prevent the deletion from happening during packaging, otherwise the web-app-creating class wouldn't actually be in the package, meaning end-user installation would fail. Maybe there's already a better way of achieving the effect I wanted.
go to post John Murray · May 25, 2023 Yes, I recommend you migrate away from using XML exports of class definitions.
go to post John Murray · Mar 9, 2023 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.
