API Foundations
What a C# application built on HiAPI needs before anything else runs: where the packages come from, what a program has to initialise, the geometry objects it passes around, and the two cross-cutting services — messages and XML serialization — that the rest of the API assumes are already there.
Ordered the way a new application meets them: getting the packages, writing the first program, then the pieces every later page takes for granted.
Starting an Application
- HiAPI Packages and Sample Code — The NuGet feed, the package dependency chain, which package a UI framework needs, and the three sample repositories
- Getting Started with HiAPI — Wiring the feed into a project, initialising and finalising the runtime, and the five steps every HiNC program follows
What Every Page Assumes
- Geometry Objects — The STL-backed interface behind every geometry type, and the basic and management geometries built on it
- Message Management — Three independent message channels — diagnostic, UI notification, application log — and why they are never mixed
- About XML IO — The serialization pattern every persisted HiAPI type implements, and the registration that must happen before a project is loaded