Repository navigation
Reference Application 0.1.0-alpha.2
Pre-release0.1.0-alpha.2 completes walkthrough Step 2: Add AsiBackbone Packages. The host now references the AsiBackbone 7.2.0 packages, and nothing is registered or wired up yet.
Important
This is an alpha pre-release. The Reference Application is an example, not a product. AsiBackbone services, governance rules, and governed endpoints are still planned.
What changed
The five AsiBackbone 7.2.0 packages are added through central package management (Directory.Packages.props), and each project's resolved graph is recorded in its packages.lock.json:
| Package | Referenced by |
|---|---|
AsiBackbone.Core |
Web, Infrastructure |
AsiBackbone.AspNetCore |
Web |
AsiBackbone.EntityFrameworkCore |
Infrastructure |
AsiBackbone.Analyzers (PrivateAssets="all") |
Web, Infrastructure |
AsiBackbone.Testing |
Tests |
Runtime behavior is unchanged: no AsiBackbone services or middleware are registered. That is Step 3, which keeps adding packages separate from changes to runtime behavior. The Release build treats analyzer warnings as errors, so AsiBackbone.Analyzers raises no findings on the NCAT-derived code.
Walkthrough status
| Step | Status |
|---|---|
| 1. Scaffold from NCAT | Complete (v0.1.0-alpha.1) |
| 2. Add AsiBackbone packages | Complete (this release) |
| 3. Register AsiBackbone services | Planned |
| 4. Define governance rules | Planned |
| 5. Govern endpoints | Planned |
| 6. Persist and verify audit evidence | Planned |
Versioning
Assemblies report version 0.1.0.0, and the informational version is 0.1.0-alpha.2+<commit>.
Changes
- Add the AsiBackbone 7.2.0 packages and complete walkthrough Step 2 (#14).
Full changelog: v0.1.0-alpha.1...v0.1.0-alpha.2