go to post Larry Overkamp · May 25, 2023 We sometimes export classes from one environment and import them to another. I don't see .cls as a supported file type for those activities.
go to post Larry Overkamp · May 19, 2023 The commonality to which I referred is for the one application only. (That may be what you were implying, not across all applications.) But the subtransform approach is still valid in this case. Thanks for the idea.
go to post Larry Overkamp · May 15, 2023 I feel that I have not explained clearly enough the Studio features that we use. We often export classes to XML files. Similarly, we import XML files, compiling them as classes during import. I didn't mean to imply that this was done simply to transfer classes to other namespaces or servers. Rather, it's a way to archive classes as XML files. (We don't use a source control system.) We use the Find in Files utility to determine the classes and other files in which a given string exists. I mentioned the Namespace variation of the Studio Workspace pane because that is the arrangement of files (classes, lookup tables, message schemas, etc.) that we most often use.
go to post Larry Overkamp · May 15, 2023 I've never used VS Code, and I don't know anything about it. I am wondering whether there are equivalents for a couple things we often do in InterSystems Studio: Export (to XML) and import classes. Find in Files. Also, is there an equivalent to the Namespace Workspace that is available in Studio? That's the arrangement we use the most.
go to post Larry Overkamp · May 30, 2018 I got it to work using the set command. Had to use "en-us", though. Can I assume that this needs to be done only once in each namespace in which it will be used? I made the change via a Terminal session; is there a way to do it in the class code (ObjectScript) itself?
