Introduction

In the next few weeks, my coworkers are planning to start using VSCode to code with InterSystems' products. Among the many advantages of that, I would emphasize being able to connect with other technologies, such as GitHub, with ease. Besides, VSCode also offers an extensive extensions store, where you can find many free add-ons that make coding faster and more efficient. Last but not least, to conquer the heart of every developer, it is open source.

Hi all, I have released the latest version of VSCode extension for ObjectScript already a month ago, and finally a time for the info about this new release.

So, what's new in the release:

What's new in this version

• added export setting "objectscript.export.addCategory" if enabled uses the previous behaviour, adds category folder to export folder, disabled by default
• added Server actions menu, by clicking on server info from status bar. Open Management portal, Class Reference and toggle connection.
• Class Suggestion in ##class, Extends, As, CompileAfter, DependsOn, PropertyClass
• $SYSTEM suggestion by Classes from %SYSTEM
• Import and compile folder or file by context menu in File Explorer
• Server Explorer, now possible to open any other namespace
• Macros suggestion

For details how it works now, look further.

If you have already built unit tests using the %UnitTest framework, or are thinking about doing so, please take a look at InterSystems Testing Manager.

Without leaving VS Code you can now browse your unit tests, run or debug them, and view previous run results.

As the announcement of Studio's deprecation has been made, users may be wondering about making a smooth transition to VS Code.

George James Software has extensive experience in VS Code, through regularly contributing to VS Code itself and building and maintaining a number of Extensions. This, combined with our expert knowledge of InterSystems technologies, gives us an in-depth understanding of what the process involves and means we have the unique capabilities to ensure a smooth migration from InterSystems Studio to VS Code.

We offer bespoke consultation, with recommendations that are tailored to your organization's specific needs. Alternatively, we will be hosting a monthly public webinar that is designed specifically for users migrating from Studio to VS Code.

If you're ready to make the switch and would like to find out more, please come and speak to us at the Global Summit next week - you'll be able to find George James Software in the Partner Pavilion. Our team will be happy to chat with you about how you can ensure your migration is seamless.

Alternatively, you can send me a direct message here on the Developer Community, or email us at info@georgejames.com.

Hi Community!

We are glad to invite every developer who uses ObjectSript and VSCode plugin to the upcoming "Introduction to VSCode-ObjectScript" webinar on April 14, 2020 at 11:00 EDT.

Speaker: @Dmitry Maslennikov, InterSystems Developers Advocate, CTO at CaretDev.

You will learn how convenient the development process can be already right now and what we are going to do next to make it even better.

Please check the agenda below.

Welcome to day 3 of Virtual Summit 2021! We have incredible content available to you this year and I'd just like to bring your attention to the 4(!) sessions that we have on Embedded Python.

The best way to list, edit, save and delete globals is using an IDE. Now, it is possible if you use VSCode. It is also possible to save globals using yaml files. Perform the following steps:

1. Get an InterSystems IRIS instance and install the application iris-global-yaml:

zpm:USER>install iris-global-yaml

2. If you just to want an InterSystems IRIS trial for tests git clone and run on docker:

Earlier this year I announced availability of a VS Code extension for coding in ObjectScript, Embedded Python or SQL using the notebook paradigm popularized by Jupyter. Today I published a maintenance release to correct a "getting started" problem.

Here's a video of the installation steps from the extension's README:

Hi developers,

We're excited to let you know about the latest release of Serenji, your on-the-spot debugger from George James Software. Version 3.2.0 focuses on the debug experience and introduces zero configuration for users. No matter where you are or what you're doing, Serenji is always ready to go in just one click, so you won't lose focus by spending time setting up a launch configuration.

This enhanced debugger also takes advantage of the latest features of VS Code itself. With this powerful combination you'll be able to smoothly identify and quickly fix errors in your code, contributing to the production of quality, maintainable code... and isn't that what everyone wants?!

In this latest release you will experience:

• Debugging in just one click with zero configuration.
• Navigation directly to the source of an error using our gj :: locate technology.
• Intuitive prompting for entrypoint and arguments.
• Configurable break on error.
• Program output in debug console.
• Run and Debug CodeLenses.
• Run multiple concurrent debug sessions and consoles.
• Shaded background for read-only documents.

If you're a new user, it's now easier for you to get started. The introduction of a welcome page Walkthrough and guidance on the Explorer and Run and Debug views means you can effortlessly create your initial workspace and start debugging.

Download Serenji directly from the VS Code marketplace and take a look at our release notes to find out more about these new features and how to use them.

We offer a free 30 day trial so if you're not yet a user of Serenji but you're interested in how it can help you, drop me a message through the Developer Community or email us at info@georgejames.com.

Happy debugging!

Are you preparing to use VS code for the first time? Just make sure you have enough privileges.

Have you defined your Iris server in your VS Code settings, and still get the following error?

VS Code accesses Iris/HealthConnect using the web application /api/atelier. If you do not have permission (i.e. you are using an LDAP user to connect and the web application is not configured to support LDAP), this is the reason why you couldn't connect.

The VS Code extension development team is looking for beta testers to provide feedback on a proposed overhaul of the client-side editing workflow. The full list of changes can be found in the GitHub pull request description. Here are the highlights:

This scenario showed up yesterday at a client site when I was delivering bespoke consultation on migration from Studio to VS Code.

It's been a while since I've posted about Embedded Git on the Developer Community, and I'd like to provide an update on the massive amount of work we've done this year and where we're going next.

Context

If you're building solutions on IRIS and want to use Git, that's great! Just use VSCode with a local git repo and push your changes out to the server - it's that easy.

But what if: