Aspire Projects
Source of truth
Local AppHost composition and native deployment-pipeline integration for .NET Aspire applications.
Contents
- ForgeTrust.AppSurface.Aspire – Core Aspire integration, including explicit deployment annotations and native publish/verify pipeline steps.
- ForgeTrust.AppSurface.Aspire.Testing – Deterministic typed profile testing for AppSurface profile-based AppHosts.
- ForgeTrust.AppSurface.Evidence.Aspire – Separate consumer-owned EvidenceHost lifecycle for explicit readiness and E2E producers; it is not a normal application AppHost extension.
ForgeTrust.AppSurface.Aspire.Tests– Tests for Aspire components.- Aspire AppHost example – Working local AppHost proof using AppSurface profiles and components.
For application-side logs, traces, and metrics that flow to the Aspire dashboard, use ForgeTrust.AppSurface.Observability in the app project. The Aspire package stays focused on AppHost composition and resource graph modeling.
Use Aspire's native testing API for AppHosts that call DistributedApplication.CreateBuilder(args) directly. Use AppSurface profile-based testing only when the AppHost selects a graph through an AspireProfile and would otherwise require asynchronously invoking AspireApp<TModule>.RunAsync(args).
For deployment artifacts, pair this package with a provider such as ForgeTrust.AppSurface.Deployment.GcpCloudRun. Aspire owns AppHost evaluation, environment selection, and pipeline ordering; AppSurface owns explicit portable intent, provider compilation, deterministic evidence, and read-only parity verification. Apply, execution, promotion, and rollback remain in the consuming release workflow.