PANiXiDA.Templates.DotnetBackend 1.0.20

PANiXiDA .NET Backend Template

Reusable .NET backend service template for PANiXiDA-style modular services.

The template produces a ready-to-build solution with:

• ASP.NET Core host;
• modular Domain/Application/Infrastructure/Presentation projects;
• PostgreSQL persistence and EF migrator;
• empty module structure ready for the first real feature;
• unit, integration, functional, and architecture tests;
• Dockerfiles for API and migrator;
• Helm values for development and production;
• GitHub Actions CI/CD workflow;
• OpenTelemetry-ready configuration.

Purpose

Use this repository as the source for a dotnet new template package. It is intended to create new backend services consistently from the command line, Visual Studio, Rider, VS Code, or any IDE that can work with .NET SDK templates.

The generated service is not supposed to keep every template artifact forever. After generation, follow TEMPLATE_FIRST_USE.md in the generated service or in this repository to create the first real feature and fill project-specific documentation.

This repository keeps source examples for template maintainers under RepositoryExamples folders. They are excluded from dotnet new output and from the NuGet template package content. Marker and assembly files stay outside that folder convention so generated services keep empty but valid projects.

Template Parameters

Example:

dotnet new panixida-backend \
  -n Acme.Billing \
  --organization Acme \
  --product Billing \
  --module Payments \
  --service-slug billing \
  --repository-name billing-service \
  --registry-owner acme

Install From The Repository

Install the template directly from a local checkout:

dotnet new install .

List installed templates:

dotnet new list panixida

Create a service:

dotnet new panixida-backend \
  -n Acme.Billing \
  --organization Acme \
  --product Billing \
  --module Payments \
  --service-slug billing \
  --repository-name billing-service \
  --registry-owner acme \
  -o Acme.Billing

Uninstall the local template:

dotnet new uninstall .

Pack And Publish As NuGet Template Package

Build a local NuGet package:

dotnet pack template/PANiXiDA.DotnetBackendTemplate.csproj --configuration Release

Install from the generated package:

dotnet new install template/bin/Release/PANiXiDA.Templates.DotnetBackend.*.nupkg

Package versions are generated by Nerdbank.GitVersioning from version.json.

Publishing to NuGet.org is handled by the publish-template job in .github/workflows/ci.yml on push to main. It uses PANiXiDA-Infrastructure/ci-cd/.github/workflows/dotnet-publish-global-nuget.yml. The repository must have:

• TEMPLATE_PROJECT variable set to template/PANiXiDA.DotnetBackendTemplate.csproj;
• NUGET_API_KEY secret with a NuGet.org API key.

After publishing, developers can install the template by package id:

dotnet new install PANiXiDA.Templates.DotnetBackend

Visual Studio And Other IDEs

This template uses the .NET SDK template engine, so the same package can be used from multiple IDEs.

Typical Visual Studio flow:

1. Install the template package with dotnet new install.
2. Restart Visual Studio if the template list was already open.
3. Open Create a new project.
4. Search for PANiXiDA or Backend Service.
5. Fill template parameters in the UI.
6. Create the solution.

Rider and VS Code can use the same template through terminal commands. IDEs that read .NET SDK templates may also show the configured parameters from .template.config/template.json and .template.config/ide.host.json.

Generated Service First Steps

After creating a service from this template:

1. Open the generated solution.
2. Read TEMPLATE_FIRST_USE.md.
3. Create the first real feature slice and initial EF migration when the model is ready.
4. Update appsettings, Helm values, CI/CD variables, README, and deployment names.
5. Run restore, format, build, test, Docker build, and Helm validation.

Repository Layout

Development

Validate the template source solution:

dotnet restore PANiXiDA.DotnetTemplate.slnx
dotnet format PANiXiDA.DotnetTemplate.slnx --verify-no-changes
dotnet build PANiXiDA.DotnetTemplate.slnx --configuration Release
dotnet test PANiXiDA.DotnetTemplate.slnx --configuration Release
dotnet pack template/PANiXiDA.DotnetBackendTemplate.csproj --configuration Release

Validate template generation locally:

dotnet new uninstall . || true
dotnet new install .
dotnet new panixida-backend \
  -n Acme.Billing \
  --organization Acme \
  --product Billing \
  --module Payments \
  --service-slug billing \
  --repository-name billing-service \
  --registry-owner acme \
  -o .tmp/generated-service

Then inspect .tmp/generated-service and run:

dotnet restore .tmp/generated-service/Acme.Billing.slnx

Remove .tmp/ after validation.

Sources

The implementation follows the .NET template engine model documented by Microsoft and the dotnet/templating project:

• Custom templates for dotnet new
• Reference for template.json