Template Comparison
This skill helps an agent compare 2+ dotnet new templates side by side so the user can
pick the right one. It inspects each template's parameters and feature support and renders
a comparison table.
When to Use
- User is deciding between similar templates (e.g.,
webapi vs webapp, blazor vs blazorwasm)
- User asks "which template should I use for X?"
- User wants to understand how two or more templates differ before creating a project
When Not to Use
- User wants to create a project — route to
template-instantiation
- User wants to author or validate a custom template — route to
template-authoring or template-validation
- User just needs to find or inspect a single template — route to
template-discovery
Inputs
| Input |
Required |
Description |
| Template short names |
Yes |
Two or more template short names to compare (e.g., webapi, webapp) |
| Comparison focus |
No |
Optional aspect to emphasize (auth, AOT, frameworks, interactivity) |
Workflow
Step 1: Inspect each template
Run dotnet new <template> --help for each template being compared to collect its
parameters (names, types, defaults, choices) and supported frameworks:
dotnet new webapi --help
dotnet new webapp --help
If a template is not installed, find and install it first (dotnet new search <keyword>,
then dotnet new install <package>).
Run --help calls sequentially. The template engine uses a global mutex, so running
several dotnet new <template> --help commands concurrently can fail with a transient
"mutex"/"persistence" error and empty output. Inspect templates one at a time; if a call
fails, retry it once before moving on, and still produce the comparison from whatever
parameter knowledge you have rather than ending with no answer.
Step 2: Build the comparison table
Produce a side-by-side table covering:
- Parameters — name, type, default, choices
- Feature support — auth, AOT, Docker, controllers, interactivity
- Available frameworks — e.g., net8.0, net9.0, net10.0
- Classifications — categories the template advertises (Web, API, Blazor, etc.)
Example shape:
| Aspect |
webapi |
webapp |
Auth (--auth) |
None, Individual, SingleOrg, Windows |
None, Individual, SingleOrg, ... |
AOT (--aot flag) |
n/a — native AOT via publish-time PublishAot |
n/a |
Controllers (--use-controllers) |
Yes |
n/a |
| Interactivity |
n/a |
n/a |
| Frameworks |
net8.0 / net9.0 / net10.0 |
net8.0 / net9.0 / net10.0 |
| Classifications |
Web, WebAPI |
Web, Razor Pages |
Step 3: Recommend
Summarize the key differences and recommend a template for the user's stated scenario,
linking to template-instantiation to create it.
Validation
Common Pitfalls
| Pitfall |
Solution |
| Comparing uninstalled templates from memory |
Install and inspect each template so the comparison reflects the real parameters and choices. |
| Assuming feature parity |
Parameter names and feature support vary by template — confirm each with --help. |
| Comparing fundamentally different template types |
Only compare templates that solve overlapping problems; note when they target different scenarios. |
More Info
1---2name: template-comparison3description: Compares two or more dotnet new templates side by side to help users choose between them based on parameters, feature support, frameworks, and classifications.4license: MIT5---67# Template Comparison89This skill helps an agent compare 2+ `dotnet new` templates side by side so the user can10pick the right one. It inspects each template's parameters and feature support and renders11a comparison table.1213## When to Use1415- User is deciding between similar templates (e.g., `webapi` vs `webapp`, `blazor` vs `blazorwasm`)16- User asks "which template should I use for X?"17- User wants to understand how two or more templates differ before creating a project1819## When Not to Use2021- User wants to create a project — route to `template-instantiation`22- User wants to author or validate a custom template — route to `template-authoring` or `template-validation`23- User just needs to find or inspect a single template — route to `template-discovery`2425## Inputs2627| Input | Required | Description |28|-------|----------|-------------|29| Template short names | Yes | Two or more template short names to compare (e.g., `webapi`, `webapp`) |30| Comparison focus | No | Optional aspect to emphasize (auth, AOT, frameworks, interactivity) |3132## Workflow3334### Step 1: Inspect each template3536Run `dotnet new <template> --help` for each template being compared to collect its37parameters (names, types, defaults, choices) and supported frameworks:3839```bash40dotnet new webapi --help41dotnet new webapp --help42```4344If a template is not installed, find and install it first (`dotnet new search <keyword>`,45then `dotnet new install <package>`).4647> **Run `--help` calls sequentially.** The template engine uses a global mutex, so running48> several `dotnet new <template> --help` commands concurrently can fail with a transient49> "mutex"/"persistence" error and empty output. Inspect templates one at a time; if a call50> fails, retry it once before moving on, and still produce the comparison from whatever51> parameter knowledge you have rather than ending with no answer.5253### Step 2: Build the comparison table5455Produce a side-by-side table covering:5657- **Parameters** — name, type, default, choices58- **Feature support** — auth, AOT, Docker, controllers, interactivity59- **Available frameworks** — e.g., net8.0, net9.0, net10.060- **Classifications** — categories the template advertises (Web, API, Blazor, etc.)6162Example shape:6364| Aspect | `webapi` | `webapp` |65|--------|----------|----------|66| Auth (`--auth`) | None, Individual, SingleOrg, Windows | None, Individual, SingleOrg, ... |67| AOT (`--aot` flag) | n/a — native AOT via publish-time `PublishAot` | n/a |68| Controllers (`--use-controllers`) | Yes | n/a |69| Interactivity | n/a | n/a |70| Frameworks | net8.0 / net9.0 / net10.0 | net8.0 / net9.0 / net10.0 |71| Classifications | Web, WebAPI | Web, Razor Pages |7273### Step 3: Recommend7475Summarize the key differences and recommend a template for the user's stated scenario,76linking to `template-instantiation` to create it.7778## Validation7980- [ ] Every template requested was inspected via `dotnet new <template> --help`81- [ ] The comparison covers parameters, feature support, frameworks, and classifications82- [ ] Differences relevant to the user's scenario are called out explicitly83- [ ] A recommendation (or clear trade-off) is provided8485## Common Pitfalls8687| Pitfall | Solution |88|---------|----------|89| Comparing uninstalled templates from memory | Install and inspect each template so the comparison reflects the real parameters and choices. |90| Assuming feature parity | Parameter names and feature support vary by template — confirm each with `--help`. |91| Comparing fundamentally different template types | Only compare templates that solve overlapping problems; note when they target different scenarios. |9293## More Info9495- [dotnet new templates](https://learn.microsoft.com/dotnet/core/tools/dotnet-new-sdk-templates) — built-in template reference96- [dotnet new](https://learn.microsoft.com/dotnet/core/tools/dotnet-new) — CLI reference
.NET (Microsoft)