Telerik.AspNetCore.Templates
1.0.1
Prefix Reserved
dotnet new install Telerik.AspNetCore.Templates@1.0.1
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
- Project template features
- Update
- Uninstall
- Development Workflow
- License
Templates
The package includes the following project templates.
| Template Name | .CLI Short Name |
|---|---|
| Telerik UI for ASP.NET Core App Admin | telerik-aspnetcore-admin |
| Telerik UI for ASP.NET Core App Admin CSP | telerik-aspnetcore-admin-csp |
| Telerik UI for ASP.NET Core App Blank | telerik-aspnetcore-blank |
| Telerik UI for ASP.NET Core App Blank CSP | telerik-aspnetcore-blank-csp |
| Telerik UI for ASP.NET Core App Dashboard | telerik-aspnetcore-dashboard |
| Telerik UI for ASP.NET Core App Dashboard CSP | telerik-aspnetcore-dashboard-csp |
| Telerik UI for ASP.NET Core App Grid | telerik-aspnetcore-grid |
| Telerik UI for ASP.NET Core App Grid CSP | telerik-aspnetcore-grid-csp |
| Telerik UI for ASP.NET Core App Grid with TabStrip | telerik-aspnetcore-grid-with-tabstrip |
| Telerik UI for ASP.NET Core App Razor | telerik-aspnetcore-razor |
| Telerik UI for ASP.NET Core App Razor CSP | telerik-aspnetcore-razor-csp |
| Telerik UI for ASP.NET Core App Standard | telerik-aspnetcore-standard |
| Telerik UI for ASP.NET Core App Standard CSP | telerik-aspnetcore-standard-csp |
CSP variants apply a strict Content Security Policy-friendly configuration. All templates support net8.0, net9.0, and net10.0.
Install
- Close Visual Studio.
- Open your Terminal or Shell app.
- Execute the
dotnet new installcommand: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:
- Go to the Command Palette at the top (
Ctrl+Shift+P). - Select Show and Run Commands.
- Select .NET: New Project...
- 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
- Open Terminal and go to the desired parent folder of your future app.
- Execute the
dotnet newcommand 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
HtmlHelperandTagHelpermarkup flavors are supported through the--markupoption (htmlortag). - The apps target
net8.0,net9.0, ornet10.0through the--projecttemplateframeworkversionoption. - 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 Telerik UI for ASP.NET Core package uses
--TelerikCoreVersion(default:*). - The Telerik UI CDN scripts use
--TelerikScriptsVersion(default:2026.3.1015). - The theme CDN version is selected by
--ThemeCDNVersion(default:14.6.1).
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:
| Template Option | Default Value | Description |
|---|---|---|
--theme |
default-ocean-blue |
Selects a Telerik theme and swatch for the Telerik UI for ASP.NET Core components. |
--ThemeCDNVersion |
14.6.1 |
Selects the CDN version used for the theme asset. |
--TelerikCoreVersion |
* |
Selects the Telerik UI NuGet package version. |
--TelerikScriptsVersion |
2026.3.1015 |
Selects the Telerik UI CDN scripts version. |
--markup |
html |
Selects the HtmlHelper or TagHelper project type. |
--projecttemplateframeworkversion |
net10.0 |
The target .NET framework version. |
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:
| Variable | Default | Description |
|---|---|---|
SELECTED_VERSION |
(empty) | Override for the Microsoft.AspNetCore.Mvc.NewtonsoftJson package version; useful when targeting a .NET preview SDK |
TEMPLATE_VERSIONS |
net8.0 net9.0 net10.0 |
Space-separated list of target frameworks to build |
TEMPLATE_MARKUPS |
html tag |
Space-separated list of markup flavors (html, tag) |
TEMPLATE_NAMES |
(all templates) | Space-separated list of template short names to build exclusively |
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
HtmlHelperandTagHelperflavors when creating a new project template, within theIndex.cshtmlfile. - Update
_Layout.cshtmlso 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
.csprojof the project template. - Add a
.template.configfolder containing configuration files used during project template generation. - Add the new template short name to the
templatesvariable inbuild-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:
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.
-
.NETStandard 2.0
- No dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.