Can we bolt VS Code editor into the Clarion IDE to replace the built in text editor?

[RchdR]

After seeing @Mark_Sarson post I wondered if we can we bolt the VS Code editor into the Clarion IDE to replace the built in #Develop text editor?

I’m guessing it does, but wanted to check first before proceeding.

Clarion Extension for VS code Version 0.3.0

VS Code Clarion Extension: New Version 0.3.0 of VS Code Extension Released! Hi everyone I’m thrilled to announce the release of version 0.3.0 of my VS Code extension. This update brings exciting new features to enhance your coding experience. What’s New in Version 0.3.0 Workspace Settings and Configuration: We’ve introduced helpful workspace settings and commands: Command: Clarion Configure ClarionProperties.xml File Use this command to configure the ClarionProperties.xml file for your w…

Clarion VS Code Extension – New Release Now Available!

Clarion VS Code Extension – New Release Now Available! V0.5.2 Hi everyone, I’m pleased to announce a new release of the Clarion Extension for Visual Studio Code! This version includes major improvements across the board — from performance to usability — and marks a shift from “experimental” to “actively maintained and production-ready.” If you’re working with Clarion source code, especially larger solutions with complex redirection setups, this update brings many enhancements you’ll a…

TIA

[MarkGoldberg]

Rich I know of no way to use a different editor inside of the clarion ide

That said IMO external editors can be a huge improvement for hand code

[Mark_Sarson]

Hi Richard,

While it might sound appealing to embed VS Code into the Clarion IDE as a replacement for the legacy #Develop editor, it’s not technically feasible. The Clarion IDE isn’t just a text editor — it’s a tightly integrated code generation environment. The editor plays a key role in managing embed points, hand-code vs generated sections, and synchronizing with the Application Tree and procedure properties. Replacing this with an external editor like VS Code would break that integration, as VS Code has no understanding of Clarion’s internal codegen model or metadata system.

Additionally, the Clarion IDE is based on a legacy fork of the #Develop IDE (SharpDevelop), which wasn’t designed for modular editor swapping. Embedding a modern editor like VS Code would require deep architectural changes, and even then, wouldn’t address the problem of Clarion’s custom embed handling, section tracking, and generation markers. While VS Code can be used effectively alongside Clarion for hand-written modules or utilities, it can’t replace the core IDE editing experience that supports application generation.

Mark

[RchdR]

I havent looked too much into the IDE so I didnt know if things like the Embed Source view was handled or not for external Text Editors to interface with, assuming external Text Editors could even handle the Clarion embeds.

I only asked because I have noticed that embed code changes for compiler errors, ultimately dont seem to be saved, like they did in the <=C6 IDE

[MarkGoldberg]

Note I don’t use .APPs
But I think you might want to look at the setting in

Tools > Applications Options > Tab[IDE] > Edit embedded source errors in generated code

[RchdR]

Its ticked at my end but I think its also a default IDE setting as well.

[MarkGoldberg]

Sorry I wasn’t clear,
I think it should be unticked

[RchdR]

I’ll give that a go, thanks!

[Jane]

Also,
Application Options > Tab[Embed Editor] Edit errors in context (using Embeditor) TICKED
Application Options > Tab[Embed Editor] Edit source embeds in context by default (using Embeditor) UNTICKED