Skip to content
Core Studio Core Studio Docs

How to: references & builds

How-to · Core Studio 3.0 · Verified 2026-09-01

Goal: give a companion real F&O context (so the language server completes X++ types) and understand exactly what every build verdict means.

Add F&O Reference…

  1. Open the picker from the companion’s context rows or the Projects pane.

  2. Pick a model from the metadata index — the Studio writes <Reference Include> entries with hint paths:

    • PackagesLocalDirectory\<Model>\bin\Dynamics.Ax.<Model>.dll
    • Microsoft.Dynamics.AX.Xpp.Support.dll
    • Microsoft.Dynamics.AX.Data.Core.dll

    — exactly Microsoft’s own C#/X++ tutorial shape, with paths resolved from the active environment profile’s metadata root (non-secret fields only).

  3. Code with F&O context — csharp-ls now resolves X++-compiled types; completion against live F&O assemblies works with zero assembly-load failures (this moment is the certified claim C-01’s proof).

Builds — the verdict law

  • Build / Rebuild (companion context rows or the Projects pane) runs the real .NET SDK build. Dirty editors are saved first (the save-dirty broadcast).
  • MSBuild diagnostics are parsed into the Problems tab with file:line navigation.
  • Every build ends with an explicit verdict line: succeeded / failed with errors / failed (exit code) / up-to-date — never silent green. A stale-output guard keeps timestamps honest.

Verify it worked

  • After referencing, DataEventType (or any F&O type) completes in the editor.
  • A deliberate error appears in Problems with a clickable file:line; the verdict line says failed with errors.

If it goes wrong

  • Assembly-load failures on F&O types — hint paths are stale; re-run Add F&O Reference… against the right profile.
  • “language server unavailable” — the pinned csharp-ls is missing; the typed state names the reason (toolchain-gate law — never silent).

Next: debugging · interop deploy.