NanoCore.Templates 10.0.2

NanoCore.Templates

dotnet new project templates for Nano.Library-based applications.

Table of Contents

• Summary
• Install
• Available Templates
• Usage
• What's Included

Summary

This package bundles the full set of dotnet new project templates for scaffolding new Nano.Library-based applications, built from the .vsTemplates repository. One install gets every template at once.

Once installed, every template appears directly in Visual Studio 2022's "Create a new project" dialog, no separate VSIX required, since Visual Studio 17.x surfaces any installed dotnet new template, and can be discovered from the CLI via dotnet new search <keyword>.

Install

dotnet new install NanoCore.Templates

Available Templates

More templates are added to this same package over time. See Nano.App.Api, Nano.App.Web, and Nano.App.Console for more on each application type.

Usage

dotnet new nanocore-api-minimal -n MyCompany.MyApi -o .\MyCompany.MyApi

-n/--name sets both the output folder name (via -o) and the generated solution/project/namespace name - every occurrence of the template's own name in file names, folder names, and file contents is replaced with the value you pass.

To update an existing installation to the latest version:

dotnet new update

What's Included

• A minimal NanoApiApplication/NanoWebApplication/NanoConsoleApplication (Program.cs), configured with no additional features enabled.
• Dockerfile / Dockerfile.Local and .docker/docker-compose.yml for local development.
• .github/workflows/build-and-deploy.yml - builds, tests, builds & pushes the container image, then deploys to AKS.
• AGENTS.md, .claude/skills/, and .github/copilot-instructions.md + .github/prompts/ - the same AI agent reference, Claude Code skills, and Copilot instructions Nano.Library ships, so an AI coding agent working in the generated repository already understands Nano's conventions from the first prompt.
• A test project using MSTest.

nanocore-api-internal additionally ships .kubernetes/*.yaml wired for Azure Managed Identity federated to Kubernetes Workload Identity, so the generated application is ready to securely access an Azure resource (Storage, SQL, Key Vault, etc.) the moment you add one, without having to plumb identity from scratch - see its own README for details.