Part-3 | Blazor WebAssembly | .Net7 API | MudBlazor

Part-3 | Blazor WebAssembly | .Net7 API | MudBlazor | CRUD - Implement Read Operation

The main objectives of this article are:

Create HTTP GET endpoint in API Project.
Consume The GET API In Blazor WebAssembly Application

Create A Service File And Implement Read Logic In API Project:

Let's create a folder like 'Services' in our API project.

Now add the 'ISuperHeroesService.cs' interface in the 'Services' folder.

API_Project/Services/ISuperHeroesService.cs:

using Dot7.Api.Data.Entities;
namespace Dot7.Api.Services
{
    public interface ISuperHeroesService
    {
        Task<List<SuperHeroes>> GetSuperHeroesAsync();
    }
}

In the 'ISuperHeroesService' interface defined method definition like 'GetSuperHeroesAsync()'.

Now add the 'SuperHeroesService.cs' class in the 'Services' folder.

API_Project/Services/SuperHeroesService.cs:

using Dot7.Api.Data.Entities;
using Microsoft.EntityFrameworkCore;
namespace Dot7.Api.Services
{
    public class SuperHeroesService: ISuperHeroesService
    {
        private readonly MyWorldDbContext _myWorldDbContext;
        public SuperHeroesService(MyWorldDbContext myWorldDbContext)
        {
            _myWorldDbContext = myWorldDbContext;
        }

        public async Task<List<SuperHeroes>> GetSuperHeroesAsync()
        {
            return await _myWorldDbContext.SuperHeroes.ToListAsync();
        }
    }
}

(Line: 7-11) Injected the 'MyWorldDbContext'.
(Line: 13-16) In 'GetSuperHeroesAsync' method we fetch the collection of records from the database.

API_Project/Program.cs:

builder.Services.AddScoped<ISuperHeroesService, SuperHeroesService>();

Create A 'SuperHeroesController' And Create A HTTP GET Endpoint:

Let's create a new controller like 'SuperHeroesController.cs'.

API_Project/Controllers/SuperHeroesController.cs:

using Dot7.Api.Services;
using Microsoft.AspNetCore.Mvc;

namespace Dot7.Api.Controllers
{
    [Route("api/[controller]")]
    [ApiController]
    public class SuperHeroesController : ControllerBase
    {
        private readonly ISuperHeroesService _superHeroesService;
        public SuperHeroesController(ISuperHeroesService superHeroesService)
        {
            _superHeroesService = superHeroesService;
        }

        [HttpGet]
        public async Task<IActionResult> GetAsync()
        {
            var results = await _superHeroesService.GetSuperHeroesAsync();
            return Ok(results);
        }
    }
}

(Line: 10-14) Injected the 'ISuperHeroesService'.
(Line: 16-21) The 'HttpGet' endpoint fetches the collection of data from the database.

Create 'SuperHeroesVm' In Blazor WebAssemply App:

First, let's create a folder like 'ViewModels' in Blazor App.

Now add the 'SuperHeroesVm.cs' in 'ViewModels' folder. Here 'SuperHeroesVm.cs' is our API response model.

BlazorWasm_Project/ViewModels/SuperHeroesVM.cs:

namespace Dot7.BlazorCrud.UI.ViewModels
{
    public class SuperHeroesVM
    {
        public int Id { get; set; }
        public string? Name { get; set; }
        public string? Franchise { get; set; }
        public string? Gender { get; set; }
        public string? ImageURL { get; set; }
    }
}

Now add the namespace in '_Import.razor'

BlazorWasm_Project/_Import.razor:

@using Dot7.BlazorCrud.UI.ViewModels

Register API Domain In Blazor WebAssembly App:

Now register the API domain in 'Program.cs'.

BlazorWasm_Project/Program.cs:

builder.Services.AddScoped(sp => new HttpClient { BaseAddress = new Uri("https://localhost:7282") });

Create A 'AllSuperHeroes.razor' Component:

First, let's create a new folder like 'SuperHeroes' in 'Pages' folder.

Now add a new component like 'AllSuperHeroes.razor' in the 'SuperHeroes' folder.

BlazorWasm_Projects/Pages/SuperHeroes/AllSuperHeroes.razor:(HTML Part)

@page "/superheroes/home"
@inject HttpClient Http

<MudContainer Class="ma-4 d-flex">
    @foreach (var item in allHeroes)
    {
        <MudCard Width="250px;" Class="mr-2">
            <MudCardHeader>
                <CardHeaderAvatar>
                    <MudAvatar Color="Color.Secondary">@item.Id</MudAvatar>
                </CardHeaderAvatar>
                <CardHeaderContent>
                    <MudText Typo="Typo.body1">@item.Name</MudText>
                </CardHeaderContent>
               
            </MudCardHeader>
            <MudCardMedia Image="@(item.ImageURL)" Height="250" />
            <MudCardContent>
                <MudText Typo="Typo.body2">Franchise - @item.Franchise</MudText>
                <MudText Typo="Typo.body2">Gender - @item.Gender</MudText>
            </MudCardContent>
           
        </MudCard>
    }
</MudContainer>

(Line: 2) The '@page' directive to configure route for blazor component.
(Line: 3) Injected the 'HttpClient' instance.
(Line: 5-26) Looping our API response to the MudBlazor card component.

BlazorWasm_Projects/Pages/SuperHeroes/AllSuperHeroes.razor:(C# Part)

@code {
    private List<SuperHeroesVM> allHeroes = new List<SuperHeroesVM>();

    protected override async Task OnInitializedAsync()
    {
        await GetAllSuperHeroesAsync();
    }

    private async Task GetAllSuperHeroesAsync()
    {
        allHeroes = await Http.GetFromJsonAsync<List<SuperHeroesVM>>("/api/superheroes");
    }
}

(Line: 2) Here initialized the instance of 'SuperHeroesVm' collection.
(Line: 4-7) The 'OnInitializedAsync' method is the blazor life cycle method.
(Line: 9-12) The 'GetAllSuperHeroesAsync' method contains logic to invoke the HTTP GET endpoint.

Enable CORS In API Project:

Let's enable CORS in API project that allows our Blazor App to consume the API endpoint.

Program.cs:

Let's run both API and Blazor WebAssembly applications.

In the next article, we will implement the Create Operation.

Support Me!
Buy Me A Coffee PayPal Me

Video Session:

Wrapping Up:

Hopefully, I think this article delivered some useful information on the.NET7 Blazor WebAssembly CRUD sample. using I love to have your feedback, suggestions, and better techniques in the comment section below.

Refer:

Part-1 | Blazor WebAssembly | .Net7 API | MudBlazor | CRUD - Create Sample SQL Table & MudBlazor Project

Follow Me:

Comments

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'

.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

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

.NET 7 Web API CRUD Using Entity Framework Core

In this article, we are going to implement a sample .NET 7 Web API CRUD using the Entity Framework Core. Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, and desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains programming functions that can be requested via HTTP calls either to fetch or update 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 the REST full services. Install The SQL Server And SQL Management Studio: Let's install the SQL server on our l

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

Angular 14 State Management CRUD Example With NgRx(14)

In this article, we are going to implement the Angular(14) state management CRUD example with NgRx(14) NgRx Store For State Management: In an angular application to share consistent data between multiple components, we use NgRx state management. Using NgRx state helps to avoid unwanted API calls, easy to maintain consistent data, etc. The main building blocks for the NgRx store are: Actions - NgRx actions represents event to trigger the reducers to save the data into the stores. Reducer - Reducer's pure function, which is used to create a new state on data change. Store - The store is the model or entity that holds the data. Selector - Selector to fetch the slices of data from the store to angular components. Effects - Effects deals with external network calls like API. The effect gets executed based the action performed Ngrx State Management flow: The angular component needs data for binding. So angular component calls an action that is responsible for invoking the API call. Aft

ReactJS(v18) JWT Authentication Using HTTP Only Cookie

In this article, we will implement the ReactJS application authentication using the HTTP-only cookie. HTTP Only Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing the 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 the authentication with HTTP-only JWT cookie then we no need to implement the 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 authenticate our client application with JWT HTTP-only cookie, I developed a NetJS(which is a node) Mock API. Check the GitHub link and read the document on G

Angular 14 Crud Example

In this article, we will implement CRUD operation in the Angular 14 application. Angular: Angular is a framework that can be used to build a single-page application. Angular applications are built with components that make our code simple and clean. Angular components compose of 3 files like TypeScript File(*.ts), Html File(*.html), CSS File(*.cs) Components typescript file and HTML file support 2-way binding which means data flow is bi-directional Component typescript file listens for all HTML events from the HTML file. Create Angular(14) Application: Let's create an Angular(14) application to begin our sample. Make sure to install the Angular CLI tool into our local machine because it provides easy CLI commands to play with the angular application. Command To Install Angular CLI npm install -g @angular/cli Run the below command to create the angular application. Command To Create Angular Application ng new name_of_your_app Note: While creating the app, you will see a noti

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

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

Tech Seeker

Search This Blog