Skip to main content

A Blazor WebAssembly CRUD Sample Using MudBlazor Components

In this article, using the MudBlazor UI component we will implement a CRUD sample in Blazor WebAssembly.

Create A Blazor WebAssembly Sample Application:

To accomplish our goal let's create a sample Blazor WebAssembly application.

Install MudBlazor Package:

Package Manager:
Install-Package MudBlazor -Version 5.0.7
.Net CLI
dotnet add package MudBlazor --version 5.0.7

MudBlazor Setup:

Add Mudblazor namespace into the '_Imports.razor'
_Imports.razor:
@using MudBlazor
Add the below CSS files inside of the head tag in 'index.html'.
wwwroot/index.html:
<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" />
Remove the CSS files like 'bootstrap.min.css' and '{your_applicationname}.style.css'.

Add MudBlazor javascript file in 'index.html' just above the closing body tag.
wwwroot/index.html:
<script src="_content/MudBlazor/MudBlazor.min.js"></script>

Register MudBlazor service in 'Program.cs'
Program.cs:
builder.Services.AddMudServices();

Add 'MudThemeProvider' component in 'MainLayout.razor'.
Shared/MainLayout.razor:

Now run the application and check the output.

Add MudAppBar Component:

Let's make our application a little pretty by adding the AppBar.
Shared/MainLayout.razor:
@inherits LayoutComponentBase
<MudThemeProvider />
<div class="page">
    <MudAppBar Color="Color.Success">
        <MudText Typo="Typo.h4" class="px-4">MudBlazor Wasm Sample</MudText>
    </MudAppBar>
    <div class="main">
        <div class="content px-4">
            @Body
        </div>
    </div>
</div>
  • (Line: 4-6) Used 'MudAppBar' and 'MudText' components.

Rest API:

In the blazor webassembly application, displaying data, storing or updating data, or removing data is carried out by Rest API. So for in our demo application, we will consume a free rest API like 'https://jsonplaceholder.typicode.com/posts'. But there are limitations with these free rest API's they won't support creating or deleting data. So in our demo for creating, update and delete operations we are going to pretend like we really calling API. 

If you have knowledge on creating rest API, then it will nice be to create a sample API with all CRUD operations and then use that API in the blazor webassembly application.

Different HttpClient Techniques:

In this demo, we are going to use the 'Type Client' technique. The 'Type Client' technique means creating a specific class to an API domain, in that class we will implement all API calls logic like fetching, updating, and deleting. So each API domain will have an individual POCO class in 'Type Client'.

Install Http Extension Package:

To use the 'Type Client' technique we need to register our POCO class in the start file using the 'AddHttpClient' service. The 'AddHttpClient' service bundled with the HTTP extension library, so need to install the library mention below.
Package Manager Command:
Install-Package Microsoft.Extensions.Http -Version 5.0.0
.Net CLI Command:
dotnet add package Microsoft.Extensions.Http --version 5.0.0

Typed HttpClient Basic Setup:

Create API payload type. So let's create a folder like 'Models' and add a class like 'Post'.
Models/Post.cs:
namespace Mud.Wasm.Sample.Models
{
    public class Post
    {
        public int Id { get; set; }
        public string Title { get; set; }
        public string Body { get; set; }
    }
}
Add the 'Post.cs' namespace into the '_Import.razor'.
_Import.razor:
@using Mud.Wasm.Sample.Models
Now let's set up our Typed HttpClient. So let's create a folder like 'ApiClient' and add a file like 'JsonPlaceHolderClient.cs'.
ApiClient/JsonPlaceHolderClient.cs:
using System.Net.Http;

namespace Mud.Wasm.Sample.ApiClient
{
    public class JsonPlaceHolderClient
    {
        private HttpClient _httpClient;
        public JsonPlaceHolderClient(HttpClient httpClient)
        {
            _httpClient = httpClient;
        }
    }
}
Add the 'JsonPlaceHolderClient.cs' into the '_Import.razor'.
_Import.razor:
@using Mud.Wasm.Sample.ApiClient
Register our 'JsonPlaceHolderClient' with our API domain.
Program.cs:
builder.Services.AddHttpClient<JsonPlaceHolderClient>(client => {
	client.BaseAddress = new Uri("https://jsonplaceholder.typicode.com");
});

Read Operation:

Let's fetch data from the API and then bind using the MudBlazor components. Let's create a method in our typed client class to fetches data from the API.
ApiClient/JsonPlaceHolderClient.cs:
public async Task<List<Post>> GetAllPost()
{
	return await _httpClient.GetFromJsonAsync<List<Post>>("/posts");
}
  • Here 'GetFromJsonAsync<T>()' method invokes the API, on receiving response it automatically deserializes the JSON response to the specified type.
In our 'Index.razor' let's bind the API call response by using MudBlazor components like 'MudPaper', 'MudContainer', 'MudProgressCircular', 'MudCard', 'MudDivider', etc.
Index.razor:(Html Part)
@page "/"
@inject JsonPlaceHolderClient _jsonPlaceHolderClient;

<MudPaper Width="100%">
    <MudContainer Style="padding-top: 5%;">
        @if (showLoader)
        {
            <MudProgressCircular Color="Color.Primary" Style="height:70px;width:70px;" Indeterminate="true" />
        }
        @foreach (var post in allposts)
        {
            <MudCard>
                <MudCardContent>
                    <MudChip Color="Color.Success">@post.Id</MudChip>
                    <MudText>@post.Title</MudText>
                    <MudText Typo="Typo.body2">@post.Body</MudText>
                </MudCardContent>
            </MudCard>
            <MudDivider />
            <MudDivider />
        }
    </MudContainer>
</MudPaper>
  • (Line: 4-5) Used 'MudPaper' and 'MudContainer' as parent components of our page.
  • (Line: 6-9) Using 'MudProgressCircular' component displaying loading spinner conditionally.
  • (Line: 12-18) Used 'MudCard' component to bind the API response.
  • (Line: 19) Used 'MudDivider' to make a nice separation between each 'MudCard'.
Pages/Index.razor:(Code Part)
@code{
    private List<Post> allposts = new List<Post>();
    bool showLoader = false;

    protected override async Task OnInitializedAsync()
    {
        showLoader = true;
        allposts = await _jsonPlaceHolderClient.GetAllPost();
        showLoader = false;
    }
}
  • The 'OnInitializedAsync' is a page life cycle method where we call our API. The 'showLoader' boolean flag enabled before invoking API and then once the response received disabled 'showLoader' flag.

Create Operation:

Initially mentioned that third-party API only supports fetching data and doesn't support any create, update, or delete operation. But we pretend our API works and we will implement the logic.

Let's add a new method for in typed client class(JsonPlaceHolderClient)
ApiClient/JsonPlaceHolderClient.cs:
public async Task<Post> CreateOrUpdatePost(Post newPost)
{
	#region  for-real-appliation-development
	// var response = await _httpClient.PostAsJsonAsync<Post>("/create", newPost);
	// return await response.Content.ReadFromJsonAsync<Post>();
	#endregion
	#region  dummy-implementation-for-demo
	await Task.FromResult(0);
	return newPost;
	#endregion
}
Now we will create a form on a popup.MudBlazor provides us a popup component that is the 'MudDialog' component.

So to use the MudBlazor dialog component first we need to render the 'MudDialogProvider' component in 'MainLayout.razor'.

For the dialog component, let's create a new blazor component like 'AddOrUpdateDialog.razor'.
Pages/AddOrUpdateDialog.razor:(Html Part)
<MudDialog>
    <DialogContent>
       <MudTextField T="string" Label="Title" @bind-Value="post.Title"/>
       <MudTextField T="string" Label="Description" @bind-Value="post.Body"/>
    </DialogContent>
    <DialogActions>
        <MudButton OnClick="Cancel">Cancel</MudButton>
        <MudButton Color="Color.Primary" OnClick="Submit">Ok</MudButton>
    </DialogActions>
</MudDialog>
  • Here rendered 'MudDialog' component that contains text fields and action buttons.
Pages/AddOrUpdateDialog.razor:(Code Part)
@code{
    [CascadingParameter] MudDialogInstance MudDialog { get; set; }

    [Parameter]
    public Post post{get;set;} = new Post();

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

    private void Submit(){
        MudDialog.Close(DialogResult.Ok<Post>(post));
    }
}
  • The 'MudDialogInstance' is cascading property that provides us control over the pop-up like closing and canceling operations. 
  • The 'post' is the 'Parameter' property whose value received from the component that invokes this dialog component.
  • The 'DialogResult.Ok<T>()' instance helps to return the response data from the dialog component.
Now we have to invoke this component to create a new record.
Pages/Index.razor:(Html Part)
@page "/"
@inject JsonPlaceHolderClient _jsonPlaceHolderClient;
@inject IDialogService _dialogService;
<div style="padding-top: 5%;">
<MudFab Color="Color.Tertiary" Icon="@Icons.Material.Filled.Add" Size="Size.Large" IconSize="Size.Large" Class="ma-2"
    @onclick="(e => Create())" 
    />
</div>

<MudPaper Width="100%">
<!-- code hidden for display purpose -->
</MudPaper>
  • (Line: 3) The 'IDialogService' injected helps to invoke the MudBlazor dialog components.
  • (Line: 5-8) The 'MudFab' button added. On clicking this button it invokes  'Create()'.
Pages/Index.razor:(Code Part)
@code{

    private async Task Create()
    {
        var parameters = new DialogParameters();
        parameters.Add("post", new Post());
        var dialog = await _dialogService.Show<AddOrUpdateDialog>("Create A Post", parameters).Result;
        
        if (dialog.Data != null)
        {
            Post newPost = dialog.Data as Post;

            await _jsonPlaceHolderClient.CreateOrUpdatePost(newPost);

            #region logic-only-for-demo
            int lastRecordId = allposts.OrderByDescending(_ => _.Id).Select(_ => _.Id).FirstOrDefault();
            newPost.Id = lastRecordId + 1;
            #endregion
            allposts.Insert(0, newPost);
        }
    }
}
  • (Line: 5-6) Preparing 'DialogParameters'. Passing empty 'Post' instance as one of the 'DialogParameters'. This helps to pass data from our 'Index.razor' component to  'AddOrUpdateDialog.razor'.
  • (Line: 7) Opens the 'AddOrUpdateDialog' component. The first parameter is heading for our dialog component, the second parameter is 'DialogParameter'.
  • (Line: 9) Checking the data from the Dialog component.
  • (Line: 13) Invoking the method that invokes API call.

Update Operation:

Now let's add an edit button to each post item card. To that edit button register a callback event method that contains logic for updating the post item.
Pages/Index.razor:(Html Part)
<MudCard>
	<!-- code hidden for display purpose -->
	<MudCardActions>
		<MudIconButton OnClick="(e => Update(post.Id))" Icon="@Icons.Material.Filled.Edit" Color="Color.Primary"></MudIconButton>
	</MudCardActions>
</MudCard>
Pages/Index.razor:(Code Part)
private async Task Update(int id)
{
	var post = allposts.Where(_ => _.Id == id).FirstOrDefault();

	var parameters = new DialogParameters();
	parameters.Add("post", post);
	var dialog = await _dialogService.Show<AddOrUpdateDialog>("Update A Post", parameters).Result;

	if(dialog.Data != null)
	{
		var dailogData = dialog.Data as Post;
		var updatedPost = await _jsonPlaceHolderClient.CreateOrUpdatePost(dailogData);

		allposts = allposts.Where(_ => _.Id != id).ToList();
		allposts.Insert(0,updatedPost);
	}
}

Delete Operation:

Now let's add a new method to our typed client(JsonPlaceHolderClient) for invoking delete API.
ApiClient/JsonPlaceHolderClient.cs:
public async Task DeletePost(int id)
{
	#region  for-real-application
	// await _httpClient.DeleteAsync($"delete?id={id}");
	#endregion

	#region dummy-implementation-for-demo
	await Task.FromResult(0);
	#endregion
}
Now add the 'Delete' button for every item of the 'Post'. Register the 'Delete' button with a callback method that contains all logic for 'post' deletion.
Pages/Index.razor:(Html Part)
<MudCard>
	<MudCardActions>
		<MudIconButton OnClick="(e => Update(post.Id))" Icon="@Icons.Material.Filled.Edit" Color="Color.Primary"></MudIconButton>
		<MudIconButton OnClick="(e => Delete(post.Id))" Icon="@Icons.Material.Filled.Delete" Color="Color.Primary"></MudIconButton>
	</MudCardActions>
</MudCard>
Pages/Index.razor:(Code Part)
private async Task Delete(int id)
{
	bool? result = await _dialogService.ShowMessageBox(
		"Warning", 
		"Deleting can not be undone!", 
		yesText:"Delete!", cancelText:"Cancel");
	
	if(result != null && result == true)
	{
	  await _jsonPlaceHolderClient.DeletePost(id);
	  allposts = allposts.Where(_ => _.Id != id).ToList();
	}
}
  • Here we use a warning message dialog box before deleting the record using 'DialogService'.
That's all about creating a blazor webassembly sample by using MubBlazor components.

Video Session:

 

Support Me!
Buy Me A Coffee PayPal Me

Wrapping Up:

Hopefully, I think this article delivered some useful information about using the MudBlazor library in the Blazor WebAssembly application. I love to have your feedback, suggestions, and better techniques in the comment section below.

Follow Me:

Comments

Post a Comment

Popular posts from this blog

.NET6 Web API CRUD Operation With Entity Framework Core

In this article, we are going to do a small demo on AspNetCore 6 Web API CRUD operations. What Is Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains a programming function that can be requested via HTTP calls to save or fetch the data for their respective clients. Some of the key characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build REST full services. Create A .NET6 Web API Application: Let's create a .Net6 Web API sample application to accomplish our

A Small Guide On NestJS Queues

NestJS Application Queues helps to deal with application scaling and performance challenges. When To Use Queues?: API request that mostly involves in time taking operations like CPU bound operation, doing them synchronously which will result in thread blocking. So to avoid these issues, it is an appropriate way to make the CPU-bound operation separate background job.  In nestjs one of the best solutions for these kinds of tasks is to implement the Queues. For queueing mechanism in the nestjs application most recommended library is '@nestjs/bull'(Bull is nodejs queue library). The 'Bull' depends on Redis cache for data storage like a job. So in this queueing technique, we will create services like 'Producer' and 'Consumer'. The 'Producer' is used to push our jobs into the Redis stores. The consumer will read those jobs(eg: CPU Bound Operations) and process them. So by using this queues technique user requests processed very fastly because actually

Part-1 Angular JWT Authentication Using HTTP Only Cookie[Angular V13]

In this article, we are going to implement a sample angular application authentication using HTTP only cookie that contains a JWT token. HTTP Only JWT Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-Only cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use authentication with HTTP only JWT cookie then we no need to implement custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To implement JWT cookie authentication we need to set up an API. For that, I had created a mock authentication API(Using the NestJS Se

Usage Of CancellationToken In Asp.Net Core Applications

When To Use CancellationToken?: In a web application request abortion or orphan, requests are quite common. On users disconnected by network interruption or navigating between multiple pages before proper response or closing of the browser, tabs make the request aborted or orphan. An orphan request can't deliver a response to the client, but it will execute all steps(like database calls, HTTP calls, etc) at the server. Complete execution of an orphan request at the server might not be a problem generally if at all requests need to work on time taking a job at the server in those cases might be nice to terminate the execution immediately. So CancellationToken can be used to terminate a request execution at the server immediately once the request is aborted or orphan. Here we are going to see some sample code snippets about implementing a CancellationToken for Entity FrameworkCore, Dapper ORM, and HttpClient calls in Asp.NetCore MVC application. Note: The sample codes I will show in

Unit Testing Asp.NetCore Web API Using xUnit[.NET6]

In this article, we are going to write test cases to an Asp.NetCore Web API(.NET6) application using the xUnit. xUnit For .NET: The xUnit for .Net is a free, open-source, community-focused unit testing tool for .NET applications. By default .Net also provides a xUnit project template to implement test cases. Unit test cases build upon the 'AAA' formula that means 'Arrange', 'Act' and 'Assert' Arrange - Declaring variables, objects, instantiating mocks, etc. Act - Calling or invoking the method that needs to be tested. Assert - The assert ensures that code behaves as expected means yielding expected output. Create An API And Unit Test Projects: Let's create a .Net6 Web API and xUnit sample applications 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. Create a fo

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

Angular 14 Reactive Forms Example

In this article, we will explore the Angular(14) reactive forms with an example. Reactive Forms: Angular reactive forms support model-driven techniques to handle the form's input values. The reactive forms state is immutable, any form filed change creates a new state for the form. Reactive forms are built around observable streams, where form inputs and values are provided as streams of input values, which can be accessed synchronously. Some key notations that involve in reactive forms are like: FormControl - each input element in the form is 'FormControl'. The 'FormControl' tracks the value and validation status of form fields. FormGroup - Track the value and validate the state of the group of 'FormControl'. FormBuilder - Angular service which can be used to create the 'FormGroup' or FormControl instance quickly. Form Array - That can hold infinite form control, this helps to create dynamic forms. Create An Angular(14) Application: Let'

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

Different HttpClient Techniques To Consume API Calls In Minimal API[.NET6]

In this article, we are going to implement different HttpClient techniques to consume API calls in minimal API. The different HttpClient techniques that we are going to explore are like: Register HttpClient Object Explicitly In DI(Dependency Injection Service) Named Client Type Client HttpRequestMessage Object Create A .NET6 Minimal API Project: Let's create a .Net6 Minimal API 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 For Minimal API Project dotnet new webapi -minimal -o Your_Project_Name Create A Third Party API Response Model: Here I'm going to use a free third-party rest API that is "https://jsonplaceholder.typicode.com/posts". So to receive the response let's create a response model like 'Post.cs'. Program.cs:(Add Post.cs c

.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