Using the Compile and Catalog Context Menu Options in VS Code

You have to be connected to the U2 server for compiling/cataloging to work [1].  For the places I consult (and my git workflow) that's usually not a great option so I end up using an ssh extension configured to download the program on open, upload on save.  After saving I'm usually bouncing to a terminal to test, and I have my own TCL wrapper so compiling cataloging is just a couple of keystrokes.

[1] https://rocketsoftware.github.io/rocket-mvbasic/usage/Connection/

[2] https://marketplace.visualstudio.com/items?itemName=Natizyskunk.sftp

Hi

We do it like Ian McGowan because the Connected Mode consume a connected u2 license (uo4Java) and you are limites to the 2 commands

With the ssh method you can create many tasks like Compile, catalogue, run,copy,.. Or run a program.

A sample, we export Sbparagraph code to a directory via trigger on XXPROCESS, sync it to the client, edit the code then run a task to sync backwards, copy into XXPROCESS and regen the executable.

Or, export from uv as json, sync, edit, and with ssh run a program to import the json into data (dict defn !) 

Or, use the concept to edit d3 program.... 

My two pences. 

Manu

I was very excited to try out the (relatively) new debugger from VSCode, which does seem to require a connected "online" folder.  I'm sure it's a VSCode requirement, but the workspace setup to get debugging going was really tricky (compare to a simple folder with a bunch of code).  And then the debugging experience was somewhat underwhelming - was hoping to have something like the program running in the terminal, a view of the code in the active editor, and debug controls off to the side.  But it's not that different from running the debugger in the terminal (at least a few months ago).  I'll stick with my favorite "N1 R" in the terminal debugger :-)

Hello Roy,
See the support ticket update we have running in parallel as you have two connection options. Catalogue, compile and debug work in both, except debugging on AIX, caused by a UniVerse side binary issue (or lack of) that we hope to resolve shortly.
Our debug functionality is using the underlying VS Code functions, so it replicates how you would debug with Python, etc in VS Code. You can, with our extension, interact with the terminal tab as well and use the "old" style RAID commands.

Christian, thanks for engaging - just one person's opinion, but the documentation at https://rocketsoftware.github.io/rocket-mvbasic/ would be much improved by having some examples of setting up an online vs offline connection, and also more detail on how a workspace should be setup (which is very confusing, but that's not Rocket's fault :-)

I can get compile, catalog and debug working on my laptop with Unidata PE installed and opening the demo account (which is offline I think), but have never been able to get them working with a remote server, which is 100% of the environments I work in.  The debugger would be a killer feature, for me at least.