DotNet Template Engine FAQs

Question 1

Can I combine multiple templates into one workflow?

Accepted Answer

Absolutely. The multi-template composition feature allows you to chain various project and item templates together into a single workflow, such as creating a new project and then immediately adding specific item templates or configurations.

Question 2

Does it support Central Package Management (CPM)?

Accepted Answer

Yes, it fully integrates with CPM. The engine automatically detects `Directory.Packages.props`, strips `Version` attributes from generated `.csproj` files, adds missing `<PackageVersion>` entries, and resolves the latest stable NuGet versions to ensure up-to-date and consistent package management.

Question 3

What is the DotNet Template Engine?

Accepted Answer

The DotNet Template Engine (Microsoft.TemplateEngine.MCP) is an MCP server enabling AI agents to interact with `dotnet new` templates through natural conversation, abstracting away complex CLI commands for template discovery, inspection, and instantiation.

Question 4

How does it simplify .NET project creation for AI agents?

Accepted Answer

Instead of rigid CLI syntax, AI agents can use natural language (e.g., "I need a web API with authentication") to define project requirements. The engine then intelligently selects the right template, resolves parameters, handles interactive elicitation, and even fetches templates from NuGet.org.

Question 5

What transport modes does the DotNet Template Engine support?

Accepted Answer

It supports both Stdio (standard I/O) for local CLI and tool usage, and HTTP for remote, multi-tenant, or CI/CD deployments. This flexibility allows integration into various development and operational environments.

DotNet Template Engine

DotNet Template Engine

主要功能

使用案例

主要功能

使用案例