Syncfusion.Blazor.Toolkit.Templates 1.0.1

Syncfusion® Blazor Toolkit Project Templates

This article describes the project templates available for building Blazor applications with the Syncfusion® Blazor Toolkit. The templates are pre-configured with Syncfusion components, theming, and project structure so you can start building applications immediately.

Prerequisites

• .NET 10 SDK
• Visual Studio 2026, JetBrains Rider, or Visual Studio Code

Verify the .NET SDK installation:

dotnet --version

Getting Started

Install the templates

dotnet new install Syncfusion.Blazor.Toolkit.Templates

Update the templates

dotnet new update

dotnet new update updates all installed template packages, not just Syncfusion.Blazor.Toolkit.Templates.

Preview available updates without installing them:

dotnet new update --check-only

Reinstall or install a specific version

dotnet new uninstall Syncfusion.Blazor.Toolkit.Templates
dotnet new install Syncfusion.Blazor.Toolkit.Templates

Install a specific version:

dotnet new install Syncfusion.Blazor.Toolkit.Templates::<version>

Available templates

Blazor Web App

Creates a project with Server interactivity (default).

dotnet new blazortoolkitweb -o MyApp

Create an Auto interactive app

Interactive components automatically switch between server and client rendering when appropriate.

dotnet new blazortoolkitweb -o MyApp -int Auto

Create an Auto interactive app with global interactivity

Applies interactive rendering at the application root.

dotnet new blazortoolkitweb -o MyApp -int Auto -ai

Interactive render mode

• Interactive server-side rendering (interactive SSR) is enabled with the Server option.
• To only enable interactivity with client-side rendering (CSR), use the WebAssembly option.
• To enable both interactive rendering modes and the ability to automatically switch between them at runtime, use the Auto (Server and WebAssembly) render mode option.
• If interactivity is set to None, the generated app has no interactivity. The app is only configured for static server-side rendering.

Interactivity location

• Per page/component (default): Interactivity is set up per page or per component.
• Global: Sets up interactivity globally for the entire app.

Interactivity location can only be set if the interactive render mode isn't None.

Blazor WebAssembly standalone app

Create a standalone Blazor WebAssembly app

dotnet new blazortoolkitwasm -o MyApp

Create a standalone Blazor WebAssembly PWA

Use the --pwa option to generate a standalone Blazor WebAssembly app with Progressive Web App support, including a service worker and web manifest.

dotnet new blazortoolkitwasm -o MyApp --pwa

Run the app

Important

When executing a Blazor Web App, run the app from the server project, which is the project with a name that doesn't end in .Client.

In a command shell opened to the project's root folder, run:

dotnet watch

The default browser is launched at https://localhost:{PORT}. To use the https launch profile, pass -lp https to dotnet watch or reorder the profiles in Properties/launchSettings.json.

To stop the app, close the browser window and press Ctrl+C in the command shell.

Additional template options

For the complete list of supported options:

dotnet new blazortoolkitweb --help

dotnet new blazortoolkitwasm --help

Visual Studio and JetBrains Rider support

After installation, the templates are available from the Create a New Project dialog in Visual Studio and the New Solution dialog in JetBrains Rider. The .NET CLI examples shown above are the recommended reference for advanced options and configuration combinations.

Additional resources

• Syncfusion® Blazor Toolkit
• ASP.NET Core Blazor project structure
• ASP.NET Core Blazor render modes
• .NET CLI

Feedback

Issues, feature requests, and contributions are welcome through the project repository.