In OS X, X is just a version 10, which in fact already replacing by 11 this year (after many years), and it's not just OS X, it's macOS.
And anyway, I would not recommend macOS for a production server, it's only suitable and supported for development.
As Kai, already mentioned, this icon, will appear only if you have any folder opened. Such a folder is a kind of project in VSCode. And, while Server Explorer view, which can be opened available by this icon, is supposed to be as just a server explorer, without editing. So, there are no reasons to make it available until any project will be opened.
First of all, you have to open this .code-workspace file with VSCode, it should offer to do it if you did not. Next, path is relevant to .code-workspace file location, and should contain own .vscode/settings.json. If all conditions are met, but behaviour not expected, please fill the issue, with examples, and screenshots, I'll try to reproduce and find the solution.
Not sure if it should work there, the minimal version of Caché is 2016.2
Could you say, what the version you use?
That’s very good to hear. As for the latest question, work in progress, and update should be available soon
Look at the project mentioned earlier. This part
{
"folders": [
{
"name": "main",
"path": "."
},
{
"name": "part1",
"path": "part1"
},{
"name": "part2",
"path": "part2"
}
]
}
Mentions three folders, where part1 and part2 supposed to be used to connect to two different servers. And each folder, have own .vscode/settings.json, which contains own settings to the server.
You can reach me directly if you would need some help with VSCode, I can help with the migration process for sure, as well.
It will be more productive than looking at the Atelier way.
Is there any reasons to install Atelier which will not be updated anymore? Why do not use VSCode with extension VSCode-ObjectScript. At the moment, this is only modern and in active development editor for InterSystems products. You can download the latest file (*.vsix) with this extension here, and install in VSCode by command Install from vsix
VSCode-ObjectScript extension which I suppose you already use, support the way, to work at the same time with multiple connections. And Mathew, gives you an example how to configure it. Look at the project. Important file there is multi.code-workspace, it's a kind of project file for VSCode, where is defined two folders, and each of those folders has its own separate settings for InterSystems. So, it means each folder will have its own connection to its own server. And you can configure as many connections as you would like. With the next release, I think it will be available one more way how to achieve the same.
<Invoke Class="Security.Users" Method="AddRoles" CheckStatus="1" >
<Arg Value="UnknownUser"/>
<Arg Value="Services_Role"/>
</Invoke>
It looks like it was added in 2020.3, not 2020.2
That's good, I should definitely test it. But 2020.2 means that it will arrive only in 2021.1 MR?
First of all, I have to investigate it by myself, so, I would have something specific to ask through WRC. At the moment, the issue I see now only on cached quires. We build our application, as separate database files with only deployed code, which we deliver to customers. And we run our tests, in the way as it works on the customer's side. The same deployed code, and for sure without cached queries.
I've already found this qualifier, and it actually does not make any difference for us. Cached query-classes, go to %sqlcq package, where it's mapped, definitely not with our code, and it also contains namespace, which will be different on the customer's side. Another solution would be to just rebuild all cached query, in the application. How it would be possible to do? As I said earlier, we test our queries for performance regressions, and not only queries, everything, and as we don't have any cache at all when we start our tests, our tests now became useless. How we can trust test's results, while the part of performance regression is just a compilation for SQL queries?
So, we have to somehow warm our application.
Writing own class queries just restore changes things, which was ok on the previous versions not an option at all even we would have much less such queries. As We don’t going to use sharping we would better to deliver our application as we did it for Caché.
We need one place where we could change the way.
We also use UnitTests, and as part of our tests we test for performance regression, and now we get some tests failed due to significant performance regression. So now we have to spend time on investigation why it’s happening. I should expect better performance when I migrate between versions, but our automatic tests doesn’t show it.
Do you mean ObjectScript code analyzer?
There is a project ObjectScript Quality formerly known as CacheQuality
This event will start in 1.5 hours
First of all, you should not think, that using docker is the same as you would install it natively. You have to build your own per-project environment with docker.
Where to find information
In addition, you would need a code editor, and you can use cross-platform VSCode with extension VSCode-ObjectScript. Brief info about how to install and configure it on Learning.
I've been using macOS Catalina, and while I'm also using docker for any project I work with, I even did not notice that it's now not supported.
So, use docker, it's very easy.
VSCode itself has support for git out of the box. So, with VSCode-ObjectScript, when you just starting to use it, you can export source code from your server, and you can send it to git.
Join me the next week on the webinar, where I'm going to speak about using git in VSCode. Also, you can look at the recording of the recent webinar from Raj Singh
And in VSCode marketplace you can find extensions for many others SCM.
What kind of issues in synchronization did you face?
If it has just Export
And what do you miss about debugging in VSCode.
You know that you always can ask me if you have any issues. ))
Do you remember, that Atelier has no future at all?
I have this in my settings.json file
"workbench.colorCustomizations": {
"activityBar.background": "#0079c9",
"activityBar.activeBackground": "#0079c9",
"activityBar.activeBorder": "#ff80cc",
"activityBar.foreground": "#e7e7e7",
"activityBar.inactiveForeground": "#e7e7e799",
"activityBarBadge.background": "#ff80cc",
"activityBarBadge.foreground": "#15202b",
"titleBar.activeBackground": "#005a96",
"titleBar.inactiveBackground": "#005a9699",
"titleBar.activeForeground": "#e7e7e7",
"titleBar.inactiveForeground": "#e7e7e799",
"statusBar.background": "#005a96",
"statusBarItem.hoverBackground": "#0079c9",
"statusBar.foreground": "#e7e7e7",
"statusBar.border": "#005a96",
"titleBar.border": "#005a96"
},This is not a part of this extension, it's just goes from VSCode itself, and marketplace can offer some extensions which can help with easy configuration of it.
As to your task, the same task will be much easier to implement in VSCode.
How to configure VSCode-ObejctScript in the InterSystems official documentation
Recording of the webinar when I give an introduction to VSCode-ObjectScript
Recording of tech talk webinar made by InterSystems PM Raj Singh, available here by registration
And register for my the next webinar where I'm going to speak about working with Git in VSCode
VSCode-ObjectScript offers some support by now, through the issues on GitHub. And anybody can order commercial support.
Documentation is there.
Atelier, too slow, and very fragile, and no improvements anymore, could you explain why do you like to use it?
If you have read the article provided above, and maybe would saw the webinar by Raj Singh very recently, where he said, that VSCode will have support through WRC quite soon when we'll reach the stable version 1.0.
Studio as well as Atelier, will not get any big improvements anymore, just only to keep it working with the newest version. While VSCode is in active development and will get a lot of new features, which will not be available in Studio.
There are multiple ways, just use Create method directly on classes Security.Roles, and Security.Users
do ##class(Security.Roles).Create(Name, Description, Resources, GrantedRoles)
do ##class(Security.Users).Create(UserName, Roles, Password)Or, you can use %Installer manifest
<Resource Name="%accounting_user" Description="Accounting" Permission="RW"/>
<Role
Name="%DB_USER"
Description="Database user"
Resources="MyResource:RW,MyResource1:RWU"
RolesGranted= /><User
Username="Clerk1"
PasswordVar="clerk1pw"
Roles="Dataentry"
Fullname="Data Entry Clerk"
Namespace=
Routine=
ExpirationDate=
ChangePassword=
Enabled=
Comment=""/>You can find what's goes to Durable SYS in the documentation
It looks like a good request for WRC, why non-interactive mode does not work in emergency mode. And maybe they can offer a workaround.