go to post Dmitry Maslennikov · Mar 8, 2021 Since 2016.2 there are no reasons to keep storing source code in XML. Even in transition process, I would recommend to store codebase based on the lowest supported version of platform. Cache and IRIS able to export and import source code in UDL format, as seen in VSCode. If you would stay with XML format just because you’d like to keep history consistent, it can be solved by converting entire history in the like it was always in UDL.
go to post Dmitry Maslennikov · Mar 7, 2021 Btw, I can add such support to any language, and what the language would you prefer next?
go to post Dmitry Maslennikov · Mar 6, 2021 It does not support. Could you explain the reasons to have this ability?
go to post Dmitry Maslennikov · Mar 5, 2021 ahh, you have a just a wrong JSON, I would recommend to find a way how to fix it from the side where it comes from. Key names in the JSON also have to be wrapped by quotes
go to post Dmitry Maslennikov · Mar 5, 2021 You can pass a stream to JSON parser. So, this code should work SET obj = {}.%FromJSON(%httprequest.HttpResponse.Data)
go to post Dmitry Maslennikov · Mar 5, 2021 Deployed classes still have to be delivered but without code, for sure, with just compiled OBJ code.
go to post Dmitry Maslennikov · Mar 4, 2021 Right, I did not said that it’s open, and available at the moment, I think how to make it the best way.
go to post Dmitry Maslennikov · Mar 4, 2021 Look at this file, the part of Language Server which communicate with IRIS https://github.com/daimor/vscode-intersystems-iris/blob/main/server/src/...
go to post Dmitry Maslennikov · Mar 3, 2021 I have a bunch of images for versions from 2014.1 with Cache and Ensemble
go to post Dmitry Maslennikov · Mar 3, 2021 Why you are using JDBC from Python, if there is pyodbc? Are you doing it in the docker container, and is it separate to IRIS container? Could you share all the components you use?
go to post Dmitry Maslennikov · Mar 2, 2021 So, your documentation link here You have to check that all the dependencies available, and LD_LIBRARY_PATH is defined correctly
go to post Dmitry Maslennikov · Mar 2, 2021 The issue could be in libraries, are you working on macOS?
go to post Dmitry Maslennikov · Feb 24, 2021 Should not be any problem if you use the same user both in Studio and VSCode. PROTECT error means you have security issue and your user not granted for write permission, or that database is just in read only mode
go to post Dmitry Maslennikov · Feb 20, 2021 Look at this page, it may help you in understanding how to configure it. If you need to store classes and mac routines separately, you can use { "objectscript.export": { "addCategory": true } } In the case of different behavior for different types, and place only mac routines to the specific folder, use this. { "obejctscript.export": { "addCategory": false, "folder": { "mac": "mac" } } }
go to post Dmitry Maslennikov · Feb 8, 2021 Check the security settings, which you can find in notes in the extension description. Add %Developer role to /api/atelier aplication GRANT EXECUTE ON %Library.RoutineMgr_StudioOpenDialog TO %Developer
go to post Dmitry Maslennikov · Feb 5, 2021 Yeah, It's a bit tricky. All the code in Caché really stored directly in the database. But with VSCode, code can be stored locally as files, for easy access and the ability to use source control such as git. After any save of the file related to Caché, e.g. Classes or routines, it will be sent to the server and compiled there. Having a separate development server, and a production server are for sure is best practice, for sure. With no permission to edit code directly on production. And with having DevOps, will be possible to build a production version and easily deploy it, by some actions or events.
