Telerik.AspNetCore.Templates 1.0.0

Telerik UI for ASP.NET Core Project Templates

This NuGet package provides ASP.NET Core project templates that include the Telerik UI for ASP.NET Core component suite. The project templates provide multiple settings to configure the Telerik UI for ASP.NET Core components during app creation.

Table of Contents

• Templates
• Install
• Use with Visual Studio
• Use with VS Code
• Use with the .NET CLI
  • Create Projects
• Project template features
  • Telerik UI for ASP.NET Core Configuration
• Update
• Uninstall
• Development Workflow
• License

Templates

The package includes the following project templates.

CSP variants apply a strict Content Security Policy-friendly configuration. All templates support net8.0, net9.0, and net10.0.

Install

1. Close Visual Studio.
2. Open your Terminal or Shell app.
3. Execute the dotnet new install command:

   dotnet new install Telerik.AspNetCore.Templates
   

Use with Visual Studio

The project templates appear in the C#, Web and ASP.NET Core categories in the Create New Project wizard.

Use with VS Code

Install the C# Dev Kit extension.

To create a new app:

1. Go to the Command Palette at the top (Ctrl + Shift + P).
2. Select Show and Run Commands.
3. Select .NET: New Project...
4. Type a project name and configure the project template options.

Use with the .NET CLI

To see all available templates, execute the dotnet new list command with the --author option:

dotnet new list --author="Progress"

For help on a specific template, execute the dotnet new command with the --help option, for example:

dotnet new telerik-aspnetcore-blank --help

Create Projects

1. Open Terminal and go to the desired parent folder of your future app.
2. Execute the dotnet new command with the short name of the template and the app name, for example:

   dotnet new telerik-aspnetcore-blank --markup tag --name MyNewAppName
   

Project Template Features

• Both HtmlHelper and TagHelper markup flavors are supported through the --markup option (html or tag).
• The apps target net8.0, net9.0, or net10.0 through the --projecttemplateframeworkversion option.
• The apps always load the Telerik UI for ASP.NET Core client-side resources (and jQuery) from CDN (jsDelivr); there is no local-files alternative.
• The apps always reference the latest Telerik.UI.for.AspNet.Core NuGet package version through a wildcard.

Telerik UI for ASP.NET Core Configuration

The project templates provide options to configure the Telerik UI for ASP.NET Core components during app creation:

Update

Execute the dotnet new update command:

dotnet new update Telerik.AspNetCore.Templates

Uninstall

To remove the currently installed package, execute the dotnet new uninstall command:

dotnet new uninstall Telerik.AspNetCore.Templates

Development Workflow

Contribution

The contents of the templates folder are the single source of truth. Any changes to the generated projects must be made in the templates folder.

After making changes, run the local build script from the repository root in Git Bash:

./build-templates-local.sh

This script packs and installs the templates from Telerik.AspNetCore.Templates.csproj, then generates and builds projects under the generated folder. The generated projects show what the templates produce for various user inputs, across all supported markups and framework versions.

Environment variables

build-templates.sh supports the following optional environment variables to limit the scope of the build:

Example — build only the telerik-aspnetcore-blank-csp template with tag markup for net10.0:

TEMPLATE_VERSIONS='net10.0' TEMPLATE_NAMES='telerik-aspnetcore-blank-csp' TEMPLATE_MARKUPS='tag' ./build-templates-local.sh

Creating new ASP.NET Core templates

• Make sure to include both HtmlHelper and TagHelper flavors when creating a new project template, within the Index.cshtml file.
• Update _Layout.cshtml so that the client-side resources can be generated automatically based on the given version, theme, and links.
• Include all the supported target frameworks within the .csproj of the project template.
• Add a .template.config folder containing configuration files used during project template generation.
• Add the new template short name to the templates variable in build-templates.sh.

How to use NuGet templates on a developer machine

To experiment with the templates outside of the templates and generated folders, pack and install them manually:

# Pack the templates NuGet package
dotnet pack

# Install the packed templates
dotnet new install bin/Debug/Telerik.AspNetCore.Templates.*.nupkg

# Create a test project
dotnet new telerik-aspnetcore-blank-csp --markup tag --output /tmp/test-core

# Uninstall when done
dotnet new uninstall Telerik.AspNetCore.Templates

Resources

The templates folder uses the dotnet templating engine. It allows user input and parameters to modify project content through replacements, conditional code, and optional pages.

Tutorials for authoring custom templates for dotnet new:

• Tutorial: Create an item template
• Tutorial: Create a project template
• Tutorial: Create a template package

GitHub resources:

• .NET Templating Wiki
  • Conditional processing and comment syntax
• .NET Template Samples
• .NET template.json Schema

License

Copyright 2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.

Packaged distributions of Progress Telerik UI for ASP.NET Core obtained from NuGet are made available pursuant to the Progress Telerik UI for ASP.NET Core EULA at https://www.telerik.com/purchase/license-agreement/aspnet-core-ui, unless you have entered into a separate MSA with the licensor.

The project templates in this package are licensed under the Apache 2.0 license. This license does not convey, override, or modify any existing licenses covering the runtime source and components of Telerik UI for ASP.NET Core. The EULA applies to those Telerik UI components, not to the template files. For more information, see the Telerik UI for ASP.NET Core license agreement.

If you don't have a license for Telerik® UI for ASP.NET Core, start a free trial and then follow the First Steps article for the appropriate ASP.NET Core application type.