Skip to content
Core Studio
Watch the product
Core Studio

Changelog

Release notes.

What changed, per version. Features mentioned here are in the shipped build and link to their documentation.

What’s new in Core Studio v3.0

The product is now Core Studio. Same product, same team — a new name from Core ERP Business Solutions. Highlights of the 3.0 line:

  • New brand throughout — window titles, splash screen, menus, installer, and shortcuts now read Core Studio. The new monochrome “C” app icon matches the Core ERP brand.
  • About dialog — Help → About Core Studio shows the version, publisher identity, and partner information.
  • Nothing moved — your settings, metadata index, chat sessions, projects, and layouts are exactly where you left them; upgrading from a 2.x install is an in-place upgrade.
  • X++ stays X++ — the language support (parser, language server, compiler bridge, .xpp files) keeps Microsoft’s language name, as always.

What’s new in v2.0

Highlights of the 2.0 line:

  • VS Code-class workbench — activity bar, side bar, editor tabs with split groups, bottom panel (Output / Problems / Terminal / AI Chat), breadcrumbs, Quick Open, and a command-center title bar.
  • Tiered metadata indexing — the AOT explorer is browsable seconds after opening a folder while the full-text index converges in the background.
  • AI Chat with tool calling — Kimi streams answers, reads and searches AOT metadata, scaffolds extensions, and writes files behind an approval gate (or Auto mode).
  • Git integration — local stage/commit/branch in the Source Control view plus user-confirmed fetch / pull / push through your system git.
  • Deployable packages & deploy pipeline — LCS-valid package creation and a build → DB sync → iisreset pipeline on OneBox VMs.
  • Self-update (this feature) — NSIS installs now check GitHub Releases on boot and every 4 hours, download updates in the background, and apply them on restart. Portable/zip builds link to the releases page instead.

Downloads publish with their complete release record (version, checksum, signing subject, notes, rollback, support path) as packages are signed and released.