go to post Scott Morrison · Jan 8, 2020 Dmitriy, I have very limited experience with VSCode, none using it with Cache coding. I looked at using it to replace UltraEdit/UEStudio and Notepad ++. I use those daily for XML, HTML file formatting, base64 decoding, file comparisons, CSS and JavaScript. Using VSCode instead of Studio isn't an option for me at this time, team uses Studio with source hooks. If that changed, I'd be open to using it side by side with Atelier to compare. I've read many of your post and other's on using VSCode for Cache development. I assumed that path was being taken as the future of Atelier was unsure, and suggested at times that it had no future, other than support for what was already there.
go to post Scott Morrison · Jan 7, 2020 I'm not using IRIS yet. Having options is good, especially for those coming from other development languages and/or not primarily focused on ObjectScript. Hopefully Studio continues to be supported, even better, receives future updates. I have no issues working in Studio. I'm primarily developing with ObjectScript and XSLT. I've also used Studio for JavaScript, CSP, and web development (mixed with ObjectScript). I'm not using Atelier now, but used it at a few previous jobs in team environments. Linking and using it with Git was very easy. After primarily using Studio for many years, adjusting to Atelier wasn't a steep learning curve. Initially there were things I switched back to Studio for, like "Find in files". But after a few updates and getting used to it, it was comfortable, flow felt logical. I haven't used VS Code for ObjectScript. I tried it recently as a potential replacement for UltraEdit/Studio. I found it cumbersome, no toolbars, not intuitive...for me. I suspect if I were to dive in with it, as I had to with Atelier, it would feel better.
go to post Scott Morrison · Feb 22, 2019 The following will work. Note, the directory must already exist. If the the file exists, it will be overwritten.Do myLogFile.LinkToFile(filename)
go to post Scott Morrison · Jul 1, 2018 Yes, I meant I don't have telnet installed. I have admin access, will install it and try connecting. I'm connecting through a VPN. Network team is also looking into it.
go to post Scott Morrison · Jun 29, 2018 I was mistaken, it's not using port 1972, but instead 19800. I am able to telnet to that machine/port from another machine, but not connect from Studio.
go to post Scott Morrison · Jun 29, 2018 I was mistaken, it's not port 1972, it's port 19800. But, that is how the connection is configured, with 19800. I can't telnet from my machine, but was able to telnet to the HealthShare server that is refusing Studio connections from another server where HealthShare is installed.
go to post Scott Morrison · Jun 29, 2018 Yes, you can do that, but it results in the same error after entering username/password and clicking OK.
go to post Scott Morrison · Jun 29, 2018 %Service_Bindings is enabled, has Password and Delegated checked, no IP restrictions.I don't believe there is a firewall issue, but will investigate that too.
go to post Scott Morrison · Jun 29, 2018 I don't get to the point of trying to login. As soon as Studio launches for this connection, instead of showing the logon box, it goes directly to the error. I've never connected to it from Studio, so my username/password are not saved. There is also no entry in the audit log when I try to open Studio, no event for this is being logged.I've also tried ccontrol stop then start on the instance.
go to post Scott Morrison · Jun 29, 2018 Studio settings:IP address = {DNS name}Port = 1972Telnet port = 23Web Server Port = 57700Atelier settings:Address = {DNS name}Web Port = 57700