CSAG Blueprint Packages

Shared Csag.Blueprint.* NuGet packages for applications built on the CSAG Blueprint. Extracted from that repository — the pre-extraction git history lives there.

Packages

Package	Description
Csag.Blueprint.Domain	Core domain contracts, entities, and Identity base types
Csag.Blueprint.Application	Application-layer abstractions, claim types, tenant context, table-view system
Csag.Blueprint.Infrastructure	BlueprintDbContext, interceptors, EF configurations, tenancy, localization
Csag.Blueprint.Web	ASP.NET Core middleware, validated options, security, FastEndpoints extensions
Csag.Blueprint.Testing	Testcontainers integration test base classes, AutoFixture support
Csag.Blueprint.SourceGenerators	Roslyn incremental source generator for translation keys

All packages are published to nuget.org and versioned in lockstep: every release bumps all six packages to the same version, and consumers must always reference all Csag.Blueprint.* packages at the same version (this avoids diamond-dependency conflicts between the layered packages).

The package architecture (generic type strategy, app-owned migrations, upgrade rules) is documented in the blueprint repository: docs/architecture/PACKAGES.md.

SDK requirement

Consuming the packages requires the .NET SDK 10.0.4xx feature band (10.0.400 or newer).

Csag.Blueprint.SourceGenerators is built against Roslyn 5.9.0, and the C# compiler refuses to load an analyzer that references a Roslyn newer than the one running the build. On an older feature band the translation-key generator is skipped with a CS9057 warning, and the generated types then surface as CS0103/CS0246 errors rather than as an obvious SDK problem.

SDK feature band	Bundled Roslyn	Generator loads
10.0.1xx	5.0.0	no
10.0.2xx	5.3.0	no
10.0.3xx	5.6.0	no
10.0.4xx	5.9.0	yes

IDEs run their own Roslyn for design-time generation, so Visual Studio / Rider must be new enough too — otherwise the generated types are missing from IntelliSense even when the command-line build succeeds.

Local development

dotnet build
dotnet pack -c Release -o ./nupkgs

Requires the .NET SDK pinned in global.json. Restore uses NuGet lockfiles (packages.lock.json); CI restores with --locked-mode, so run dotnet restore after changing dependencies to refresh the lockfiles.

Release process

This repository follows the neolution-ch release playbook (Changesets, NuGet variant):

1. Every PR that changes a package needs a changeset: run pnpm changeset, pick any one package (all six are a fixed group — they bump together), choose the bump type, and describe the change. CI blocks PRs without one.
2. On merge to main, the Release workflow maintains a "chore: version packages" PR that accumulates pending changesets (versions synced into the .csproj files via scripts/sync-versions.mjs).
3. Merging that PR creates git tags and GitHub Releases; the NuGet Publish workflow then packs and pushes all packages to nuget.org.

Conventions:

• The packages are on a 0.x version: breaking changes are declared as minor changesets, fixes as patch. Prerelease channels (alpha/beta/rc) are reserved for staging 1.0.0 later.
• Every release that changes the EF model must call it out in the changeset so consumers know to generate a migration (see the upgrade rules in PACKAGES.md).
• Dependabot PRs get changesets generated automatically. Manual dependency bumps in Directory.Packages.props do not trip the changeset check — add a changeset yourself.