#VSCode

Hi Community,

As you may know, we successfully held InterSystems Developers Meetup in Boston at Global Summit 2019. And now it's time to find out which solutions development on InterSystems IRIS have been discussed!

Please welcome the Meetup video recording on InterSystems Developers YouTube Channel:

⏯ InterSystems Developers Meetup - Global Summit 2019

https://www.youtube.com/embed/PUnZwDxqEZM
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

The latest release of Serenji by George James Software introduces zero configuration debugging, so it's ready to go in just one click - no matter where you are or what you're doing, your on-the-spot debugger is ready to go. 

We have introduced a host of new features to enhance the debugging experience so you can focus on identifying and fixing errors, without losing focus by spending time setting up a launch configuration. 

Check out the new features in our release notes. 

If you've already started using Serenji 3.2.0 let us know how you're getting on! 

When start docker in VSCode:

C:\Git\ESKLP2\ESKLP>docker-compose build --no-cache
ERROR: The Compose file '.\docker-compose.yml' is invalid because:
Unsupported config option for services.iris: 'init'

Why? Please, help

Hi Community,

We're pleased to invite you to the upcoming webinar in Hebrew:

👉VS Code - Beyond the Basics 👈

📅 Date & time: February 6th, 3:00 PM IDT

https://www.youtube.com/embed/uT5sqSwtF0k
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

The most recent release of Serenji features our innovative gj::locate technology. It was a standalone tool we originally created for a Developer Community contest earlier this year, but we've incorporated it into our debugger after some great feedback from developers. 

It works by navigating you directly to the source of your server-side errors in just a couple of clicks - enabling you to quickly fix errors without the need to count tedious lines of code... and let's be real, who has got time for that when you're under pressure to fix this bug? 

It's simple and straightforward to use:

1. Click on the gj::locate panel in the status bar

2. Enter the ObjectScript error message or line reference from a class/.mac routine..

3. gj::locate then does the work for you by taking you straight to the corresponding line in your source code.

Easy peasy... and with time to spare to make yourself a coffee before your deadline! 

The video below shows it in action - let us know if you've already given it a go. Or, if you're interested in trying it out we offer a free 30 day trial license, just drop me a message through the Developer Community or email us at info@georgejames.com.

Hi,

Is there a way to include a prefix for the instance name in the server connection? I have 1 server with multiple iris instances, using 1 webserver. Each instance can be reached using a prefix in the url: (for example https://localhost/instance1/...).

I want to use VS code remote, but can't add the prefix to the hostname (or ip), and also not to the port, as this is numeric. Any idea how to solve this?

In VS Code using the InterSystems ObjectScript extensions, I'd like the indentation applied to match that of IRIS Studio. Specifically for comments and dot syntax, I'd like pressing enter (carriage return) to preserve the current dot depth and same comment beginning.

In IRIS Studio after changing the indentation settings to custom using " \t.#/;" without quotes (note the leading space), the behaviour looks like this:

Every class on the server throws this same error when trying to run the debugger. I've already made sure I don't have the %SecureBreak role assigned which seems to typically fix this issue. Any advice on how to troubleshoot this would be greatly appreciated!

Error is : <COMMAND>zDebugStub+40^%Debugger.System.1

GitLab is using the rouge ruby gem, that apparently does not support ObjectScript at the moment. Is there an easy way to add syntax highlighting to GitLab ?

Hey Developers,

Please welcome the new video by @Ron Sweeney on InterSystems Developers YouTube:

⏯ Hands Off HealthShare Deployment Workflow with GitLab Runners

https://www.youtube.com/embed/NP_smt5UY3c
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

Gitlab Runners and InterSystems Healthshare Code Deployment and VSCode oh my. More details in this post.

Hi,

i'm starting to try to switch to VS Code with ISC integration plugins.
Everything seems fine until i get to and environment with CCR enabled. I can't open any class in RW and i don't know how to check the class out.

Is it supported? What do i need to do to use it?

Thanks

Pietro

Come and say hi to us in the Partner Pavilion at the Global Summit!

We’ll be showcasing our Serenji on-the-spot debugger which has undergone some big changes in the last year—users can now enjoy a seamless debugging experience with zero configuration, along with taking advantage of the latest features in VS Code itself, enabling users to smoothly identify and quickly fix errors in your code, contributing to the production of quality, maintainable code.

If you want to see Serenji in action look for us in the Partner Pavilion, we'll be on hand to show you a demo. Prospective users are also welcome to join our User Group Session during the lunchtime session on Wednesday, June 22nd. Email laurelj@georgejames.com to let us know you'll be there.

I am trying to adjust my VSCode settings.json to make my repository to Server Side Source Control. When Adding "uri" to the settings.json to change the setting but VSCode is telling me that the Property uri is not allowed.

Why is this happening?

I have a VS Code workspace using server-side editing with separate folders for different namespaces on the instance: