Technical documentation
September 12, 2026 · View on GitHub
This section explains the scaffolding implementation and how to extend generated applications. For command usage, see the user guide.
| Document | Questions covered |
|---|---|
| Architecture and key flows | How the CLI generates projects, how each process architecture runs, and how automatic changes protect user code |
| Module lifecycle | Service registration, initialization order, page injection, and resource ownership |
| Navigation contract | Page registration and integration with standard or custom windows |
| Recipe contract | Component metadata, file plans, project operations, updates, and removal |
| Project manifest | Module origins, file hashes, baselines, and compatibility boundaries |
After changing core mechanisms, run dotnet test src/XamlNexus.TemplateTests/XamlNexus.TemplateTests.csproj. For generated-project dependencies, templates, or build configuration, also run the generated-project acceptance script. Automated tests check code and generated structure. WinUI builds check compilation. GUI behavior and installation upgrades require separate runtime checks.