go to post John Murray · Apr 17, 2021 And we're airborne! Server Manager 2.0 is now published on VS Marketplace. If you are quick you can be the first to review it there.
go to post John Murray · Apr 16, 2021 Sounds like you are using the client-side editing paradigm. As Dmitry says, unless you haven't installed Language Server it will be LS that initially handles your "Go to Definition" request. But I think LS then calls an API entrypoint named serverDocumentUriForUri in the main ObjectScript extension (OS) to find out where the target document should be fetched from. As the API name indicates, this returns a uri (a document reference) that always fetches code from the server. And since you are using the client-side editing paradigm the fetched code cannot be edited. Please open an issue on the repo at https://github.com/intersystems-community/vscode-objectscript/issues where it can be tracked and managed better than in this DC post.
go to post John Murray · Apr 16, 2021 @Andrea Schecker-Krauss do you also get ECONNREFUSED if you try to import a single file?
go to post John Murray · Mar 30, 2021 See https://community.intersystems.com/post/vscode-tips-tricks-web-terminal for a recent tip from @Tani Frankel about integrating WebTerminal into VS Code.
go to post John Murray · Mar 10, 2021 Am I correct that there's some kind of relationship between the Speedminer tools and Intersystems DeepSee Visual Reporting?
go to post John Murray · Feb 26, 2021 See https://community.intersystems.com/post/diagnosing-cause-errors for tips on finding out more about what's causing <PROTECT> errors.
go to post John Murray · Feb 24, 2021 Are some classes in a package that is mapped to a different database that you don't have WRITE permission on?
go to post John Murray · Feb 5, 2021 @Sorin Fratila you may like to point your BE colleagues at this recording of a Developer Community webinar I co-presented last May titled "Enterprise Grade Source Code Management" https://youtu.be/iVxTu_jPHBg
go to post John Murray · Feb 4, 2021 If the BE guys are currently all working on the same copy of the codebase in a shared namespace on the production server, I think it will be an easier transition if they adopt server-centric source control such as Deltanji from my employer George James Software. They could start off by putting the production namespace under source control, then evolve to an architecture where development happens in a different shared namespace (could be on the same server, or on a different server), or separate namespaces for each developer, feeding an integration namespace where testing happens. Deltanji is very flexible and configurable, plus the configuration can be changed as the team's needs change. It integrates with Studio and VS Code editing tools. Evaluation copies of Deltanji are available, and we're happy to set up PoCs for development organizations who are interested in trying it out for themselves. We can put people in touch with existing users, and some of those users might post a response on this thread too. John MurraySenior Product EngineerGeorge James Softwarehttps://georgejames.com
go to post John Murray · Jan 27, 2021 @Marcel den Ouden please make sure the things you miss have already been reported. And if they haven't, open a new issue for them. One item per issue please, unless items are very closely related. "Maintain social distancing"
go to post John Murray · Jan 27, 2021 Please give us more details of your question. If it is hard to explain, maybe paste a screenshot that you have drawn on.
go to post John Murray · Jan 27, 2021 AFAIK the InterSystems ObjectScript extension for VS Code doesn't yet implement a convenient way of overriding an inherited method or property. I suggest you use VS Code's 'Report Issue' option from the Help menu to file a Feature Request on the extension. That dialog is a convenient way to route your request to the correct repo.
go to post John Murray · Jan 4, 2021 Is Git a mandatory requirement for you? If not, did you consider our Deltanji product? Your source code gets managed within the environments it executes in, with no need for export/import to files nor for a separate build/deploy toolchain. Deltanji is fully supported on Cache 2018 and Studio, as well as on InterSystems IRIS. It's also well integrated with VS Code. John MurraySenior Product EngineerGeorge James Softwarehttps://georgejames.com
go to post John Murray · Dec 11, 2020 @Rich Taylor Working direct on the server using the isfs FileSystemProvider first arrived in 0.7.12 on Aug 29, 2019.
go to post John Murray · Dec 11, 2020 @Rich Taylor wrote: One thing to keep in mind is that all code that you create or edit in VSCode is stored locally on your development machine That is not necessarily true. The model of working in which code is stored and source-controlled on an InterSystems server is perfectly valid, fully supported, and suits some teams and organizations better than the model that uses client-side source files and file-based source control tools such as Git. See here for how this is done when using the InterSystems ObjectScript extension in VS Code. IIRC the internal applications team at InterSystems works this way. Our Serenji extension also uses the server-side model.
go to post John Murray · Dec 11, 2020 That's one of the benefits of using George James Software's Deltanji for your source control. As well as code versioning you get highly configurable deployment facilities. Here's a recording of me using Deltanji integrated with VS Code to transfer to my test namespace the two classes I've been working on as part of a task.
go to post John Murray · Sep 11, 2020 Glad you like it! We just released 0.9.2, so everyone can try this out by simply updating extensions. At the same time we released a new version of Server Manager. Now you can define a new connection direct from the server selection quickpick. Less need to go into the JSON files. Feedback welcome, here or in the GitHub repos of the two extensions.
go to post John Murray · May 21, 2020 Sounds like your team all work in shared namespace(s) on a Caché server. Server-side source control is the way to go. We just gave a webinar about our Deltanji tool doing exactly this. Watch out for the recording appearing on the Developer Community YouTube channel soon.