Blazor WebAssembly App using .NET Core CLI

9 Aug 20214 minutes to read

This article provides a step-by-step introduction to configure Syncfusion Blazor setup, and also to build and run a simple Blazor WebAssembly application using the .NET Core CLI.

Starting with version 17.4.0.39 (2019 Volume 4), you need to include a valid license key (either paid or trial key) within your applications. Please refer to this help topic for more information.

Prerequisites

.NET Core SDK 3.1.8 / .NET 5.0 SDK

Create a Blazor WebAssembly project using .NET Core CLI

Run the following command line to create a new Blazor WebAssembly application.

dotnet new blazorwasm -o WebApplication1
cd WebApplication1

If you have installed multiple SDK versions and need any specific framework version (net5.0/netcoreapp3.1) project, then add -f flag along with dotnet new blazorwasm comment. Refer here for the available options.

Installing Syncfusion Blazor packages in the application

You can use any one of the below standards to install the Syncfusion Blazor library in your application.

Using Syncfusion Blazor components individual NuGet Packages [New standard]

Starting with Volume 4, 2020 (v18.4.0.30) release, Syncfusion provides individual NuGet packages for our Syncfusion Blazor components. We highly recommend this new standard for your Blazor production applications. Refer to this section to know the benefits of the individual NuGet packages.

Now, add Syncfusion.Blazor.Calendars NuGet package to the new application using the following command line. For more details about available NuGet packages, refer to the individual NuGet Packages documentation.
```
 dotnet add package Syncfusion.Blazor.Calendars -v '{:nuget-version:}'
 dotnet restore
```
The Syncfusion Blazor Calendars package will be included in the newly created project once the installation process is completed.
Add the Syncfusion bootstrap4 theme in the <head> element of the ~/wwwroot/index.html page.
```
 <head>
     ....
     ....
     <link href="_content/Syncfusion.Blazor.Themes/bootstrap4.css" rel="stylesheet" />
 </head>
```
WARNING

Syncfusion.Blazor package should not be installed along with individual NuGet packages. Hence, you have to add the above Syncfusion.Blazor.Themes static web assets (styles) in the application.

Using Syncfusion.Blazor NuGet Package [Old standard]

WARNING

If you prefer the above new standard (individual NuGet packages), then skip this section. Using both old and new standards in the same application will throw ambiguous compilation errors.

Now, add Syncfusion.Blazor NuGet package to the new application using the following command line.
```
 dotnet add package Syncfusion.Blazor -v '{:nuget-version:}'
 dotnet restore
```
The Syncfusion Blazor package will be included in the newly created project once the installation process is completed.
Add the Syncfusion bootstrap4 theme in the <head> element of the ~/wwwroot/index.html page.
```
 <head>
     ....
     ....
      <link href="_content/Syncfusion.Blazor/styles/bootstrap4.css" rel="stylesheet" />
 </head>
```
The same theme file can be referred through the CDN version by using https://cdn.syncfusion.com/blazor/19.3.43/styles/bootstrap4.css.

Adding Syncfusion Blazor component and running the application

Open ~/_Imports.razor file and import the Syncfusion.Blazor namespace.
```
 @using Syncfusion.Blazor
 @using Syncfusion.Blazor.Calendars
```

Open the ~/Program.cs file and register the Syncfusion Blazor Service.

 using Syncfusion.Blazor;

 namespace WebApplication1
 {
     public class Program
     {
         public static async Task Main(string[] args)
         {
             ....
             ....
             builder.Services.AddSyncfusionBlazor();
             await builder.Build().RunAsync();
         }
     }
 }

We can disable the dynamic script loading and refer to the scripts from the application end by using the IgnoreScriptIsolation parameter in AddSyncfusionBlazor() at the program.cs. For more details, please refer here for how to refer custom/CDN resources.

Now, add the Syncfusion Blazor component in any .razor file in the ~/Pages folder. For example, the calendar component is added in the ~/Pages/Index.razor page.
```
 <SfCalendar TValue="DateTime"></SfCalendar>
```
Run dotnet run command to run the application. The Syncfusion Blazor Calendar component will be rendered in the web browser.