MPCore.Localization 0.9.0

MP Core

A backend framework for .NET 10 that makes the decisions every service makes again: how a command runs, who opens and commits the transaction, how a message leaves with that transaction, how a failure becomes an HTTP or gRPC answer, how a token is validated, where logs and traces go. MP Core makes them once, with tests, and ships them as NuGet packages, a project template and a command-line generator.

You run one command, get a complete and secure backend, and write only your business logic.

dotnet tool install --global MPCore.Cli --version 0.9.0
dotnet new install MPCore.Templates::0.9.0

mpcore new backend --organization Acme --component Orders --output ./orders \
  --shape modular-monolith --transport both --messaging kafka \
  --cache hybrid --business-audit postgresql

What you get

What MP Core is not

• It holds no business logic. No product entity, status or rule lives in the framework.
• It is not a login server. A backend validates a token; sign-in belongs to an identity provider such as Keycloak.
• It is not event sourcing, and not CQRS over two databases. Commands and queries are separate messages over one PostgreSQL database by default.

Learn it

A generated repository carries its own guides (docs/architecture.md, docs/capabilities.md, src/Modules/README.md) and skills for AI coding assistants (.mpcore/skills), written for the options you chose.

Packages

docs/guide/packages.md says what each one is for.

Build and test this repository

dotnet restore MPCore.sln --locked-mode
dotnet build MPCore.sln --configuration Release --no-restore
dotnet test MPCore.sln --configuration Release --no-build

Unit tests need nothing else. The integration tests run against real services and are skipped unless these variables name them:

docker compose -f eng/compose.test.yaml up -d starts all three with the values the CI workflow uses.

Versioning

MP Core follows Semantic Versioning. While the major version is 0, a minor version may change the public API; release notes say what changed and how to move. Three rules hold from now on (ADR-010):

• A published version is never rebuilt with different bytes. A corrected build takes the next version.
• The runtime packages, the CLI and the template ship together, as one cohort under one version.
• A generated repository references an exact version, never a range.

Contributing and security

CONTRIBUTING.md says how to propose a change. To report a vulnerability, follow SECURITY.md; do not open a public issue for it.