Porting & project practice
Evidence basis: source-verified at the pinned commit. Claims on this page were checked by reading the CNA source at commit c1c316b9; unless a sentence says otherwise, nothing here was built or executed.
Migration and porting practice, case studies, spec auditing, samples and examples, project conventions and the road ahead.
Pages in this group
- Migrating an XNA game to CNA: a process that keeps every mismatch attributable — A porting process for XNA and FNA games at this snapshot: freeze a baseline, translate mechanically, map assets and shaders to real routes, pick renderers by evidence and verify in rungs.
- Porting case studies: the Blupi games, the official samples and the example catalogue — What real ports around CNA teach: a native-CNA port plan for a reconstructed Blupi game, the Speedy Blupi 2013 port, cna-samples and cna-examples, each pinned.
- 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.
- Project records as evidence: plans, ledgers, versions, handoffs and re-audits — How to use and write CNA's plans, handoffs, audits and gates as evidence: roles, stable task IDs, executable ledgers, version coordinates, defect-ledger rules and documentation re-audits.