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

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

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

.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

GraphQL API Integration In Asp.Net Core Application

Introduction: GraphQL is a query language for your API and a server-side runtime for executing queries by using a type system you define for your data. GraphQL can be integrated into any framework like ASP.NET, Java, NestJs, etc and it isn't tied to any specific database or storage engine and is instead backed by your existing code and data. How GraphQL API Different From Rest API: GraphQL exposes a single end-point or route for the entire application, regardless of its responses or actions. HTTP-POST is the only Http verb recommended by the GraphQL. The client applications (consumers of API) can give instructions to GraphQL API about what type of properties to be returned in the response. Building Blocks Of GraphQL API: The main building blocks of GraphQL API is Schemas and Types.  A 'Schema' in GrpahQL API describes the functionality available to the clients connect to API. Schema mostly consists of GraphQL Object Types, Queries, Mutations, etc. T

ASP.NET Core Web API Versioning

Introduction: An iteration and evolutionary changes of an ASP.NET Core Web API is handled by Versioning. Versioning of an API gives confidence to the clients which consumes API for a long time. Any changes or development of an API will be accessible using the new version and it won't cause issues to the clients consuming the old version of API. When To Use Versioning: Any API response changes. Developing an API by implementing testing levels like 'Alpha', 'Beta', and 'RC' versions before releasing Production. Deprecating an API which means API going to be removed or upgraded by a version within a short period. Versioning Types: Query String Versioning Url Path Versioning Media Type Versioning API Version Nuget: To Configure versioning to AspNet Core Web API Microsoft provided a library(Microsoft.AspNetCore.Mvc.Versioning). So to use the versioning library please install NuGet below.              Install-Package Microsoft.A

Blazor Server CRUD Operations

Introduction: Blazor Server is a web framework to develop server-side single-page applications. Blazor is made up of components with the combinations on C#, Html, CSS.  Blazor Server is production-ready from the .Net Core 3.0.  Blazor Server Working Mechanism: Blazor Server is a very light-weight web development framework.  In Blazor Server, not all code gets downloaded to the client browsers. Blazor Server made of components these components can be a block of code or page with respective navigation.  Blazor server application communicates with the server with a SignalR background connection which is inbuilt functionality. Application click,  form submission, change events, application page navigation every operation is carried out by the SignalR connection by communicating with the server.  Blazor updates the Html DOM very gently on every data update without any overhead. Blazor Server application maintains a nice intelligent tree structure to update the required inform