Telerik.Blazor.Templates
1.1.1
Prefix Reserved
dotnet new install Telerik.Blazor.Templates@1.1.1
Telerik UI for Blazor Project Templates
This NuGet package provides ASP.NET Core Blazor project templates that include the Telerik UI for Blazor component library. The project templates provide multiple settings to configure the Telerik Blazor 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
- License
Templates
The package includes the following project templates.
| Template Name | .CLI Short Name |
|---|---|
| Telerik Blazor Web App | telerik-blazor |
| Telerik Blazor WebAssembly Standalone App | telerik-blazorwasm |
| Telerik Blazor MAUI Hybrid App | telerik-blazor-maui |
Install
- Close Visual Studio.
- Open your Terminal or Shell app.
- Execute the
dotnet new installcommand:dotnet new install Telerik.Blazor.Templates
Use with Visual Studio
The project templates appear in the C#, Web and Blazor categories in the Create New Project wizard. Make sure to select "All platforms" in the respective dropdown.
When creating a Web App with WebAssembly or Auto render mode, make sure to select the server project as a startup project before running.
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-blazor --help
To create a new Blazor app:
- 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-blazor -o MyNewAppName
Project Template Features
- The Blazor Web Apps use a Global interactivity location, i.e. interactive render mode for the entire app. This is the easier and recommended way to integrate Telerik UI for Blazor.
- The WebAssembly apps reference the latest minor version of the selected .NET version through a wildcard.
- The apps use the
httpslaunch profile by default. - Visual Studio opens
Home.razorautomatically after the app is created.
Telerik UI for Blazor Configuration
- New Telerik Blazor apps reference the latest Telerik UI for Blazor version with a wildcard
*. - The Telerik UI for Blazor NuGet package, namespaces, service, and static assets are added, according to best practices.
- The Web App template sets
PrivateAssets="none"to the Telerik UI for Blazor NuGet package reference when using WebAssembly or Auto render mode. This avoids license warnings on app startup.
The project templates provide options to configure the Telerik UI for Blazor components during app creation:
| Template Option | Default Value | Description |
|---|---|---|
| Theme | Default | The Telerik UI for Blazor NuGet package includes a few CSS files that define different styling of the Telerik Blazor components. |
| Icon type | SVG | Telerik Blazor components can render SVG icons or font icons. |
Update
Execute the dotnet new update command:
dotnet new update Telerik.Blazor.Templates
Uninstall
To remove the currently installed package, execute the dotnet new uninstall command:
dotnet new uninstall Telerik.Blazor.Templates
License
The Telerik® UI for Blazor project template 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 Blazor. For more information, see the Telerik® UI for Blazor license agreement.
If you don't have a license for Telerik® UI for Blazor, start a free trial and then follow the First Steps article for the appropriate Blazor 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.