Skip to content
Core Studio Core Studio Docs

Tutorial: coming from Visual Studio

Tutorial · Core Studio 3.0 · Verified 2026-09-01

Persona: F&O developer fluent in the Visual Studio extension · Time: one session · Requires: the packaged app; your usual AOT root.

Independent user-acceptance testing scored the Studio’s code-authoring experience above the Visual Studio reference — a positive deviation, not parity. But a switch is a switch. This page sets expectations the honest way.

What maps 1:1 (muscle memory works)

  • Ctrl+P quick open, F1 command palette, F12 / Ctrl+Click go to definition, split editors, tabs, breadcrumbs.
  • Problems panel for diagnostics — model issues separated from collapsed environment noise, clickable to the line.
  • Source control — status, stage, commit, branch (see “deliberately different” for the boundary).
  • Themes: WCAG-AA-tested dark and light.

What’s deliberately different

  • No Visual Studio required. The Studio is standalone — it drives Microsoft’s own compiler and toolchain, but the IDE itself is ours.
  • The index is always fresh. The Visual Studio cross-reference rebuild runs on its own schedule; here it’s current on every save. Expect “who uses this?” to be a milliseconds question, not an afternoon one.
  • Local-only git. Push and pull stay in the terminal, by design — the panel never touches remotes or your credentials. Publishing half-compiled work is a non-goal.
  • Honest unavailable states. Off the D365 VM, build/deploy commands show exactly why they’re unavailable instead of failing later or silently.
  • AI is governed. The assistant can look, propose, and explain — mutating actions stop at a human approval gate, deny by default.

What to know before you switch

Set these expectations now and the switch is smooth:

  • X++ debugging — shipped: net8-class coverage, dual-PDB, typed degraded states, the live-AOS guard’s both death classes. C# companion debugging (.NET 8+) is shipped with its own documented boundaries.
  • WYSIWYG form/report canvas — the report canvas is shipped and certified: pixel-accurate drag-and-drop RDL editing, layout truth only (it never renders data; live preview stays typed-unavailable — deploy + execute is the fallback). A pixel-accurate form canvas remains roadmap.
  • In-IDE X++ test execution — shipped: SysTests run in the Testing view through the SysTestConsole provider, UAT-verified. The generated CI stage (headless SysTestConsole) is the addition for pipeline runs.

If it goes wrong