Skip to main content

Blazor Server CRUD Operation Using MudBlazor UI Components[.NET6]



In this article, we are going to implement CRUD operation in .NET6 Blazor Server application using the MudBlazor UI components.

Blazor Server:

Blazor Server is a single-page application. At the server, a pre-rendered HTML output of the page will be delivered to the user browsers. Any UI update, event handling, javascript calls will carry over by a SingnalR connection to the server. So application updates are depending on the continuous connection of the SignalR.

So Blazor server is a single-page application that can be made of C#. Since the blazor server only outputs the pre-rendered HTML to the client, so there is no c# code downloading into user browsers like in Blazor WebAssembly(c# code downloaded and run in the browser for blazor webassembly application).

SignalR Connection:

A Blazor Server application works over a SignalR connection. A Blazor Server application creates a UI State memory at the server which will be interacted by the SignalR connections. If a SignalR connection got interrupted, then the client tries to maintain the same state of the application by initiating a new SignalR connection and uses the existing UI state memory at the server. App routing changes, event changes, data changes everything will be carried out by the SignalR connection without any page reload.

Each browser screen or browser tab has its own SignalR Connection channels and UI states at the application. So each browser screen or browser tab acts as an individual user request.

Blazor Components:

Blazor Server application built on top of the 'Blazor Components'. A Blazor component file will be created like 'Example.razor', the file extension is '.razor'. A blazor component file consists of both c# and razor syntax. Blazor component also provides an option to split the file like 'Example.razor'(contains all razor code) and 'Example.razor.cs'(contains all c#code).

Create A .NET6 Blazor Server Application:

Let's create a .Net6 Blazor Server sample project to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor.
CLI command
dotnet new blazorserver -o your_project_name

Let's understand a few key things about the project:
Route Middleware:- 
Program.cs:
  • The 'app.MapBlazorHub()' middleware is to enable the SignalR routing. The 'app.MapFallbackToPage()' middleware is to load the 'Pages/_Host.cshtml' so this is entry file gets loads.
Pages/_Host.cshtml:-
  • In Blazor Server '_Host.cshtml' is the entry file. We can observe here we configured the master layout that is '_Layout.cshtml'. Here 'App.razor' component is the entry component of the Blazor Sever.
App.razor:-
  • This is the blazor routing component. The 'RouteView' component to navigate to the respective Blazor Component.
wwwroot:-
The 'wwwroot' folder contains static  files like 'js', 'css', 'images',etc.

Install And Configure MudBlazor UI Library:

Run the below command to install the MudBlazor UI library.
Package Manager:
Install-Package MudBlazor -Version 6.0.2

.NET CLI Command:
dotnet add package MudBlazor --version 6.0.2

Now add the MudBlazor namespace like '@using MudBlazor' into the '_Imports.razor' file.

Now add the below CSS links into 'Pages/_Layout.csthml' inside of the 'Head' HTML tag.
<link href="https://fonts.googleapis.com/css?family=Roboto:300,400,500,700&display=swap" rel="stylesheet" />
<link href="_content/MudBlazor/MudBlazor.min.css" rel="stylesheet" />
Now remove the existing CSS files inside of the 'Pages/_Layout.cshtml'.

Now add a Mudblazor js file into the 'Pages/cshtml' just above the closing body tag.
<script src="_content/MudBlazor/MudBlazor.min.js"></script>
In .NET6 'Startup.cs' file is excluded all service registration added to the 'Program.cs' file. Now let's register the MudBlazor service into the 'Program.cs' file.
Program.cs:
builder.Services.AddMudServices();
Now let's replace the content in 'Shared/MainLayout.razor' file.
Shared/MainLayout.razor:
@inherits LayoutComponentBase

<PageTitle>Dot6.BlazorServer.Crud.Learn</PageTitle>

<MudThemeProvider />
<MudDialogProvider />
<MudSnackbarProvider />

<MudLayout>
    <MudAppBar Color="Color.Primary">
        <MudText Typo="Typo.h4">Cakes Wold</MudText>
    </MudAppBar>
    <MudMainContent class="mt-4">
        @Body
    </MudMainContent>
</MudLayout>
  • (Line: 5) The 'MudThemeProvider' component was added as global registration. It helps apply styles or colors to our sample application.
  • (Line: 6) The 'MudDialogProvider' component was added as global registration. It is required to work with MudBlazor dialog.
  • (Line: 7) The 'MudSnackbarProvider' component was added as global registration. It is required to display notification messages.
  • (Line:  9&16) The 'MudLayout' component was added as a parent of all other components.
  • (Line: 10-12) The 'MudAppBar' component added display a nice header menu.
  • (Line: 13-14) The '@Body' a razor syntax that helps to render the Blazor page components and it was wrapped by the 'MudMainContent' component. The 'class="mt-4"'(margin-top) applying some margin between the 'MudAppBar' and 'MudMainContent' components.
Now let's run the application and check our app design.

SQL Sample Script:

Run the below script to create a table into the SQL server.

CREATE TABLE [dbo].[Cake] (
    [Id]          INT             IDENTITY (1, 1) NOT NULL,
    [Name]        VARCHAR (MAX)   NULL,
    [Price]       DECIMAL (18, 2) NULL,
    [Description] VARCHAR (MAX)   NULL
);

Install EntityFramework Core And Configure Database Context:

Install entity framework core library.
Package Manager:
Install-Package Microsoft.EntityFrameworkCore -Version 6.0.0

Package Manager:
dotnet add package Microsoft.EntityFrameworkCore --version 6.0.0

Install EFCore dependant SQL library.
Package Manager:
Install-Package Microsoft.EntityFrameworkCore.SqlServer -Version 6.0.0

Package Manager:
dotnet add package Microsoft.EntityFrameworkCore.SqlServer --version 6.0.0

Now let's create a table class like 'Cake.cs'.
Data/Entities/Cake.cs:
namespace Dot6.BlazorServer.Crud.Learn.Data.Entities;
public class Cake
{
    public int Id{get;set;}
    public string Name{get;set;}
    public decimal Price{get;set;}
    public string Description{get;set;} 
}
Now let's create the Database Context model like 'MyWorldDbContext.cs'
Data/Entities:
using Dot6.BlazorServer.Crud.Learn.Data.Entities;
using Microsoft.EntityFrameworkCore;

namespace Dot6.BlazorServer.Crud.Learn.Data;
public class MyWorldDbContext : DbContext
{
    public MyWorldDbContext(DbContextOptions<MyWorldDbContext> options) : base(options)
    {
        
    }
    public DbSet<Cake> Cake{get;set;}
}
Add the 'Cake.cs' and 'MyWorldDbContext.cs' namespace into the '_Import.razor'.
_Import.razor:
@using Dot6.BlazorServer.Crud.Learn.Data
@using Dot6.BlazorServer.Crud.Learn.Data.Entities
Add the database connection string into 'appsettings.Development.json' file.
appsettings.Development.json:
"ConnectionStrings":{
    "MyWorldDbConnection":"your_connection"
}
Register the DatabaseContext.
Program.cs:
builder.Services.AddDbContext<MyWorldDbContext>(options =>
{
    options.UseSqlServer(builder.Configuration.GetConnectionString("MyWorldDbConnection"));
});

Read Operation:

let's implement logic to read the records from the database and bind them to the UI. Let's update the Index.razor component as below
Index.razor:(Html Code)
@page "/"
@inject MyWorldDbContext _myworldDbContext;

<MudGrid Justify="Justify.Center" class="pr-4 pl-4">
    @foreach (var cake in allCakes)
    {
        <MudItem xs="3">
            <MudCard>
                <MudCardHeader>
                    <CardHeaderContent>
                        <MudText Typo="Typo.body1">@cake.Name</MudText>
                        <MudText Typo="Typo.h6">@cake.Price $</MudText>
                    </CardHeaderContent>
                </MudCardHeader>
                <MudCardMedia Image="images/sample-cake.jpg" Height="250" />
                <MudCardContent>
                    <MudText Typo="Typo.body2">@cake.Description</MudText>
                </MudCardContent>
                <MudCardActions>
                    <MudIconButton Icon="@Icons.Filled.Edit" Color="Color.Primary" />
                    <MudIconButton Icon="@Icons.Filled.Delete" Color="Color.Error" />
                </MudCardActions>
            </MudCard>

        </MudItem>

    }

</MudGrid>
  • (Line: 2) Injected the 'MyWorldDbContext'.
  • (Line: 4) Rendered the 'MudGrid' component. Here applied padding right&left like 'class="pr-4 pl-4"'.
  • (Line: 5-27) Looping the collection of records by rendering the 'MudItem' component, inside it renders the 'MudCard' component.
  • (Line: 15) Added a dummy image for display purposes(image added in folders of  'wwwroot/images').
Index.razor:(C# Code)
@code {
    List<Cake> allCakes = new List<Cake>();
    protected  override async Task OnInitializedAsync()
    {
        allCakes = await _myworldDbContext.Cake.ToListAsync();
    }
}
  • (Line: 2)Initialized the collection of 'Cake' instance.
  • (Line: 3-6) The 'OnInitialized' life cycle method invokes the database call to fetch all the records.

 Create Operation:

Let's implement logic to add a new record to the database.

Now let's create dialog components like 'AddOrUpdateCakeDailog.razor'.
Pages/AddOrUpdateCakeDailog.razor:(HTML Part)
<MudDialog>
    <DialogContent>
        <MudTextField T="string" Label="Name" @bind-Value="cake.Name" />
        <MudTextField T="decimal" Label="Price" @bind-Value="cake.Price" />
        <MudTextField T="string" Label="Description" @bind-Value="cake.Description" Lines=4/>
    </DialogContent>
    <DialogActions>
        <MudButton OnClick="Cancel">Cancel</MudButton>
        <MudButton Color="Color.Primary" OnClick="Submit">Ok</MudButton>
    </DialogActions>
</MudDialog>
  • (Line: 1&11)Here added the 'MudDialog' component. 
  • (Line: 3&4) The 'MudTextField' component for the text fields and '@bind-value' for 2-way binding.
  • (Line: 5) The 'MudTextField' component can be rendered as multi-line text filed by adding attributes like 'Lines'.
  • (Line: 8) Added 'Cancel' button and its click event with 'Cancel' method.
  • (Line: 9) Added 'Ok' button and its click event with 'Submit' method.
Pages/AddOrUpdateCakeDailog.razor:(c# Part)
@code {
    [CascadingParameter] MudDialogInstance MudDialog { get; set; }

    [Parameter] public Cake cake { get; set; } = new Cake();

    private void Cancel()
    {
        MudDialog.Cancel();
    }

    private void Submit()
    {
        MudDialog.Close(DialogResult.Ok<Cake>(cake));
    }
}
  • (Line: 2) The 'MudDialogInstance' property gives control over the dialog.
  • (Line: 4) The 'cake' property instance is used to bind the dialog fields and the instance of the property comes from the component that invokes the dialog.
  • (Line: 6-9) The 'Cancel' method to close the dialog.
  • (Line: 11-14) The 'Submit' method closes the dialog as well passe the dialog information to a component that invokes the component.
Index.razor:(HTML Part)
@page "/"
@inject MyWorldDbContext _myworldDbContext;
@inject IDialogService _dialogService;

<MudContainer Class="d-flex justify-center mb-2">
    <MudFab Color="Color.Primary" Icon="@Icons.Material.Filled.Add" Size="Size.Large" IconSize="Size.Large" Label="Add A New
    Cake" Class="ma-2" @onclick="(e => CreateAsync())" />
</MudContainer>
<MudGrid Justify="Justify.Center" class="pr-4 pl-4">
   <!-- Code hidden for display purpose -->
</MudGrid>
  • (Line: 3) Injected the 'IDialogService'.
  • (Line: 5-8) Add button, its click event registered with 'CreateAsync()' method.
Index.razor:(C# Part)
private async Task CreateAsync()
{
	var parameters = new DialogParameters();
	parameters.Add("cake", new Cake());
	var dialog = await _dialogService.Show<AddOrUpdateCakeDialog>("Create A Post", parameters).Result;

	if (dialog.Data != null)
	{
		Cake newCake = dialog.Data as Cake;
		_myworldDbContext.Cake.Add(newCake);
		await _myworldDbContext.SaveChangesAsync();

		allCakes.Insert(0, newCake);
	}
}
  • (Line: 3-4) The 'DialogParameters' instance needs to use for adding parameters that can be sent to the dialog.
  • (Line: 5) Using the 'IDialogService' we can open dialog by calling 'Show<T>()' where T(type) will be the dialog component. The 'Show<T>' has 2 params where 1st parameter will be the title for the dialog and 2nd parameter will be the data that passed to the dialog component.
  • (Line: 7) Checking for data coming from the dialog.
  • (Line: 9-11) Using entity framework database context saves the new record to the database.
  • (Line: 13) Now updating the 'allCakes' collection property with our newly created record.


Update Operation:

Let's implement our logic to update the record.
Index.razor:(HTML Part)
<MudCardActions>
	<MudIconButton Icon="@Icons.Filled.Edit" Color="Color.Primary" @onclick="(e => UpdateAsync(cake.Id))" />
	<MudIconButton Icon="@Icons.Filled.Delete" Color="Color.Error" />
</MudCardActions>
  • (Line: 2) The edit button registers with the 'UpdateAsync' click event.
Index.razor:(C# Part)
private async Task UpdateAsync(int id)
{
	var parameters = new DialogParameters();
	var cakeNeedToUpdate = allCakes.FirstOrDefault(_ => _.Id == id);
	parameters.Add("cake", cakeNeedToUpdate);
	var dialog = await _dialogService.Show<AddOrUpdateCakeDialog>("Update A Item", parameters).Result;
	if (dialog.Data != null)
	{
		var updatedCake = dialog.Data as Cake;
		_myworldDbContext.Cake.Update(updatedCake);
		await _myworldDbContext.SaveChangesAsync();

		allCakes.Remove(cakeNeedToUpdate);
		allCakes.Insert(0, updatedCake);
	}
}
  • (Line: 3-5) Adding the record that needs to be updated as a parameter to the 'DailogParamters'.
  • (Line: 9-11) Saving modified changes to the database.


Delete Operation:

Let's implement our logic to remove the record from the database.
Index.razor:(Html Part)
<MudCardActions>
	<MudIconButton Icon="@Icons.Filled.Edit" Color="Color.Primary" @onclick="(e => UpdateAsync(cake.Id))" />
	<MudIconButton Icon="@Icons.Filled.Delete" Color="Color.Error" @onclick="(e => DeleteAsync(cake.Id))" />
</MudCardActions>
  • (Line: 3) The 'Delete' button registered with 'DeleteAsync' click event
Index.razor:(C# Part)
private async Task DeleteAsync(int id)
{
	bool? result = await _dialogService.ShowMessageBox(
	"Delete Confirmation",
	"Deleting can not be undone!",
	yesText: "Delete!", cancelText: "Cancel");

	if (result ?? false)
	{
		var cakeToRemove = await _myworldDbContext.Cake.FindAsync(id);
		_myworldDbContext.Cake.Remove(cakeToRemove);
		await _myworldDbContext.SaveChangesAsync();

		allCakes.Remove(cakeToRemove);
	}
}
  • (Line: 3-6) MudBlazor 'MessageBox' are simple popups that can be easily used like 'warning' or 'confirmation' popups. So 'MessageBox' is also invoked by using 'IDialogService'. MessageBox on click 'cancelText' button returns 'null', if we click 'yesText' button then it returns 'true' value.
  • (Line: 10-12) Deleting the record from the database.

Support Me!
Buy Me A Coffee PayPal Me

Video Session:

Wrapping Up:

Hopefully, I think this article delivered some useful information on Blazor Server CRUD operations Using MudBlazor UI components. I love to have your feedback, suggestions, and better techniques in the comment section below.

Refer:

Follow Me:

Comments

Popular posts from this blog

Blazor WebAssembly Custom Authentication From Scratch

In this article, we are going to explore and implement custom authentication from the scratch. In this sample, we will use JWT authentication for user authentication. Main Building Blocks Of Blazor WebAssembly Authentication: The core concepts of blazor webassembly authentication are: AuthenticationStateProvider Service AuthorizeView Component Task<AuthenticationState> Cascading Property CascadingAuthenticationState Component AuthorizeRouteView Component AuthenticationStateProvider Service - this provider holds the authentication information about the login user. The 'GetAuthenticationStateAsync()' method in the Authentication state provider returns user AuthenticationState. The 'NotifyAuthenticationStateChaged()' to notify the latest user information within the components which using this AuthenticationStateProvider. AuthorizeView Component - displays different content depending on the user authorization state. This component uses the AuthenticationStateProvider

How Response Caching Works In Asp.Net Core

What Is Response Caching?: Response Caching means storing of response output and using stored response until it's under it's the expiration time. Response Caching approach cuts down some requests to the server and also reduces some workload on the server. Response Caching Headers: Response Caching carried out by the few Http based headers information between client and server. Main Response Caching Headers are like below Cache-Control Pragma Vary Cache-Control Header: Cache-Control header is the main header type for the response caching. Cache-Control will be decorated with the following directives. public - this directive indicates any cache may store the response. private - this directive allows to store response with respect to a single user and can't be stored with shared cache stores. max-age - this directive represents a time to hold a response in the cache. no-cache - this directive represents no storing of response and always fetch the fr

.Net5 Web API Managing Files Using Azure Blob Storage

In this article, we are going to understand the different file operations like uploading, reading, downloading, and deleting in .Net5 Web API application using Azure Blob Storage. Azure Blob Storage: Azure blob storage is Microsoft cloud storage. Blob storage can store a massive amount of file data as unstructured data. The unstructured data means not belong to any specific type, which means text or binary data. So something like images or pdf or videos to store in the cloud, then the most recommended is to use the blob store. The key component to creating azure blob storage resource: Storage Account:- A Storage account gives a unique namespace in Azure for all the data we will save. Every object that we store in Azure Storage has an address. The address is nothing but the unique name of our Storage Account name. The combination of the account name and the Azure Storage blob endpoint forms the base address for each object in our Storage account. For example, if our Storage Account is n

.Net5 Web API Redis Cache Using StackExchange.Redis.Extensions.AspNetCore Library

In this article, we are going to explore the integration of Redis cache in .Net5 Web API application using the 'StackExchange.Redis.Exntensions' library. Note:- Microsoft has introduced an 'IDistributedCache' interface in dotnet core which supports different cache stores like In-Memory, Redis, NCache, etc. It is simple and easy to work with  'IDistributedCache', for the Redis store with limited features but if we want more features of the Redis store we can choose to use 'StackExchange.Redis.Extensions'.  Click here for Redis Cache Integration Using IDistributedCache Interface . Overview On StackExchange.Redis.Extnesions Library: The 'StackExchange.Redis.Extension' library extended from the main library 'StackExchange.Redis'. Some of the key features of this library like: Default serialization and deserialization. Easy to save and fetch complex objects. Search key. Multiple Database Access Setup Redis Docker Instance: For this sampl

Endpoint Routing In Asp.Net Core

How Routing Works In  Core 2.1 And Below Versions?: In Asp.Net Core routing is configured using app.UseRouter() or app.UseMvc() middleware. app.UseMvc(routes => { routes.MapRoute( name: "default", template: "{controller=Home}/{action=Index}/{id?}"); }); Here in Dotnet Core version 2.1 or below versions on the execution of route middleware request will be navigated appropriate controller matched to the route. An operation or functionality which is dependent on route URL or route values and that need to be implemented before the execution of route middleware can be done by accessing the route path from the current request context as below app.Use(async (context, next) => { if(context.Request.Path.Value.IndexOf("oldvehicle") != -1) { context.Response.Redirect("vehicle"); } else { await next(); } }); app.UseMvc(routes => { routes.MapRoute( name: "vehicleRoute", template: "vehicle", defaul

Asp.Net Core MVC Form Validation Techniques

Introduction: Form validations in any applications are like assures that a valid data is storing on servers. All programing frameworks have their own individual implementations for form validations. In Dotnet Core MVC application server-side validations carried on by the models with the help of Data Annotations and the client-side validations carried by the plugin jQuery Unobtrusive Validation. jQuery Unobtrusive Validation is a custom library developed by Microsoft based on the popular library  jQuery Validate . In this article, we are going to learn how the model validation and client-side validation works in Asp.Net Core MVC Application with sample examples. Getting Started: Let's create an Asp.Net Core MVC application project using preferred editors like Microsoft Visual Studio or Microsoft Visual Studio Code. Here I'm using Visual Studio. Let's create an MVC controller and name it as 'PersonController.cs' and add an action method as bel

NestJS File Upload

In this article, we are going to understand the steps to create a file uploading endpoint in the NestJS application. Key Features In NestJS File Upload: Let us know some key features of NestJS file upload before implementing a sample application. FileInterceptor: The 'FileInterceptor' will be decorated on top of the file upload endpoint. This interceptor will read single file data from the form posted to the endpoint. export declare function FilesInterceptor(fieldName: string, localOptions?: MulterOptions): Type<NestInterceptor>; Here we can observe the 'fieldName' first input parameter this value should be a match with our 'name' attribute value on the form file input field. So our interceptor read our files that are attached to the file input field. Another input parameter of 'MulterOptions' that provides configuration like file destination path, customizing file name, etc. FilesInterceptor: The 'FilesInterceptor' will be decorated on t

.NET Core MVC Application File Upload To Physical Location With Buffered Technique

Buffering Technique In File Upload: The server will use its Memory(RAM) or Disk Storage to save the files on receiving a file upload request from the client.  Usage of Memory(RAM) or Disk depends on the number of file requests and the size of the file.  Any single buffered file exceeding 64KB is moved from Memory to a temp file on disk.  If an application receives heavy traffic of uploading files there might be a chance of out of Disk or RAM memory which leads to crash application. So this Buffer technique used for small files uploading. In the following article, we create a sample for the file uploading using .NET Core MVC application. Create The .NET Core MVC Project: Let's create a .NET Core MVC project, here for this sample I'm using Visual Studio Code as below.   Check the link to use the Visual Studio Code for .NET Core Application . IFormFile: Microsoft.AspNetCore.Http.IFormFile used for file upload with buffered technique. On uploading files f

Ionic Picker Sample Code In Angular

Introduction: Ionic Picker(ion-picker) is a popup slides up from the bottom of the device screen, which contains rows with selectable column separated items. The main building block of ion-picker as follows: PickerController PickerOptions PickerController: PickerController object helps in creating an ion-picker overlay. create(opts?: Opts): Promise<Overlay> PickerController create method helps in create the picker overlay with the picker options PickerOptions: PickerOptions is a configuration object used by PickerController to display ion-picker. Single Column Ionic Picker: single.item.picker.ts: import { Component } from "@angular/core"; import { PickerController } from "@ionic/angular"; import { PickerOptions } from "@ionic/core"; @Component({ selector: "single-column-picker", templateUrl:"single.item.picker.html" }) export class SingleItemPicker { animals: string[] = ["Tiger&quo

.Net Core HttpClient JSON Extension Methods Using System.Net.Http.Json Package

.Net Core 3.0 onwards Microsoft brought up a new package called System.Net.Http.Json. This new package provides JSON extension methods for HttpClient. These JSON extension methods will have a prebuild mechanism for serializing or deserializing response data or payload of HttpClient call. System.Net.Http.Json extension methods that are provided to HttpClient, few of them are mentioned below. GetFromJsonAsync PostAsJsonAsync PutAsJsonAsync ReadFromJsonAsync In this article, we understand System.Net.Http.Json package by implementing the HttpClient samples by with and without JSON extension methods and compare them. Create A .Net Core Web API Sample Application: Let's create a .Net Core sample Web API application, from this application we will consume another Web API by implementing HttpClient calls. We can create a Web API sample application using IDE like Visual Studio 2019(Supports .Net Core 3.0 plus) or  Visual Studio Code . Create A Typed Client: In .Net Core using the Http