Public header index

CNA snapshot 009d40f5 · Development › Generated References · source links pinned to 009d40f5

✓

Evidence basis: source-verified at the pinned commit. Claims on this page were checked by reading the CNA source at commit 009d40f5; unless a sentence says otherwise, nothing here was built or executed. A tree-shape inventory; it does not distinguish supported API from headers that merely sit under include/.

ℹ

Generated page. Produced by python3 scripts/generate_dev_reference.py from the Git objects of CNA commit 009d40f5; do not edit it by hand. It is a syntactic inventory: it locates declarations and files, and does not establish behaviour, build success or test results.

808 non-Internal CNA/Microsoft headers21 modules

⚠

“Public” is a tree-shape term here. The lists below are headers under include/CNA or include/Microsoft, outside Internal. That includes the XNA-shaped surface. Export macros and target install rules remain authoritative for what a shipped binary actually exposes, and the experimental C ABI (modules/c-api/include/CNA/C, ABI 0.29.0) is separately versioned.

audio (22)

c-api (61)

content (56)

content-pipeline (104)

core (15)

design (14)

devices (33)

devices-ext (18)

diagnostics (2)

gamer-services (54)

graphics (144)

graphics-ext (98)

input (51)

inspector (3)

math (24)

media (24)

net (23)

phone (9)

platform (27)

runtime (23)

storage (3)

Deep dives on this topic

Long-form pages that explain the exact semantics, invariants and evidence behind this subject.

Auditing the XNA API surface: the census, xna4-spec and two worked audits — How CNA's 331/331 and 3,627/3,627 API census is produced and read, which reference settles which question, and worked surface audits of Ray and Viewport against XNA's own IL.
Avatars: the inert XNA API and the skinned extension — Why CNA's XNA avatar classes report Unavailable and draw nothing, and how the opt-in SkinnedModelEXT path samples clips, builds the bone palette, tints parts and loads its content.
CNAEXT catalogue: extension surfaces by namespace — A catalogue of CNA's non-XNA surface at snapshot 009d40f5, namespace by namespace, with member names, reasons and boundaries, how much the CNAEXT marker covers, and what the strict check proves.
ContentManager resolution, caching and failure rules — Which file ContentManager::Load<T> actually reads, what RootDirectory does and does not confine, what the cache keeps, and which exception each tier throws at this snapshot.
Core framework and graphics API map — An orientation map of CNA's core framework and graphics API: owning headers, public shape, the boundary that trips ports, and where each behaviour is explained, for math, framework, content, resources, effects and device state.
From C# to C++: CNA's translation conventions — How CNA represents C# XNA concepts in C++ so that code stays diffable against the reference: names, properties, aliases, events, interfaces, disposal, visibility, layout and the porting checklist.
GamerServices behaviour contract — What CNA's GamerServices does without Xbox LIVE: the four local identities, persisted achievements and leaderboards, the Guide dialogs the game draws, the inert members and the dispatcher hang.
Native C API contract: admission, buffers, retention and route families — What CNA's C ABI 0.29.0 version checks admit, the exact count-then-copy protocol, callback and registration lifetimes, resources that retain others, caller-created devices and all 61 headers by family.
Network sessions and the SystemLink protocol — What each NetworkSessionType really does in CNA, the SystemLink wire and discovery protocols, the trust model, delivery guarantees, host migration and the evidence behind them.

Known issues in this area

Current defects, gaps and limitations at this snapshot that touch this subject.

CNA-BUG-025: PlaneIntersectionType's Doxygen swaps the meaning of Front and Back — PlaneIntersectionType.hpp documents Front as the negative half-space and Back as the positive one, the opposite of what every CNA classification returns and of XNA's meaning.
CNA-GAP-003: CNA::Runtime and CNA::RuntimeOptions are declared in CNA/Misc.hpp but not implemented — The runtime module's public include path declares a CNA::Runtime subsystem facade with documented behaviour, but no translation unit defines it, so any call fails to link; CNA knows and guards the fact with a CMake check

The same subsystem is explained at four altitudes. These are the neighbouring pages at each one.

User guide: XNA compatibility · Experimental C API
Maintainer workflow: Change public XNA behavior · Update the C API
Reference: Module index