Skip to main content

.NET5 Razor Pages CRUD Operations Using Entity Frame Work Core

In this article, we will implement a sample application .Net5 Razor Pages CRUD operations using entity framework core.

Razor Pages:

Razor Page is a simplified web application model. On comparing with 'MVC' template, razor pages won't have 'Controller', which means razor pages is a combination of 'Views' and 'Models'. Routing itself configured within the page or view. A razor page mostly contains 2 files like 'filename.cshtml'(view) and 'filename.cshtml.cs'(model).

Create A .Net5 Razor Page Application:

Begin our journey by creating a .Net5 razor page template application.

Visual Studio users it is very easy to create razor applications by selecting the template option like 'ASP.NET Core Web APP'.

Here I'm using a visual studio code editor and .Net CLI commands to generate the application.
CLI Command To Create Razor Page Application:
dotnet new webapp -n your_project_name
After creating the project few basic things we must aware of like:

Endpoint Middleware -  Middleware to set up the routing for our razor page application. This configuration is done in 'Startup.cs'

_ViewImports.cshtml -
File used to configure application namespaces

_ViewStart.cshtml -  File helps to load the master layout template.

Shared/_Layout.cshtml - Default master template.

wwwroot - Folder to maintain static files like 'css', 'js', 'images', etc.

appsettings.{environment variable name}.json - Configuration file.

Entity Framework Core:

Entity Framework Core is an Object/Relational Mapping(ORM) framework. EF Core makes database communication more fluent and easy. 
EF Core supports:
  • Database First Approach.
  • Code First Approach.
Code First Approach means first we will create c# POCO classes and then create the database tables. Code First Approach has one more sub-category like 'Code First With Existing Database'. So the 'Code First With Existing Database' can work with the already created tables in the database which is an ideal choice for real-time development. Our demo will be implemented using 'Code First With Existing Database'.

Install EF Core Nuget:

Now install ef core and SQL ef core extension Nuget package into our application.
Package Manager(Visual Studio):
Install-Package Microsoft.EntityFrameworkCore -Version 5.0.6
Install-Package Microsoft.EntityFrameworkCore.SqlServer -Version 5.0.6
CLI Commands(Visual Studio Code):
dotnet add package Microsoft.EntityFrameworkCore --version 5.0.6
dotnet add package Microsoft.EntityFrameworkCore.SqlServer --version 5.0.6

Sample SQL Script:

To follow the demo, run the SQL script to generate the table.
CREATE TABLE [dbo].[Gadgets](
	[Id] [int] IDENTITY(1,1) NOT NULL,
	[ProductName] [varchar](max) NULL,
	[Brand] [varchar](max) NULL,
	[Cost] [decimal](18, 0) NOT NULL,
	[ImageName] [varchar](1024) NULL,
	[Type] [varchar](128) NULL,
	[CreatedDate] [datetime] NULL,
	[ModifiedDate] [datetime] NULL,
PRIMARY KEY CLUSTERED 
(
	[Id] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]

Setup EF Core DbContext:

First, let's create POCO class that represents our table. So let's create a new folder 'Data', inside of it create one more folder like 'Entities'. Inside of the 'Entities' folder creates our POCO class.
Data/Entities/Gadgets.cs:
namespace Dotnet5.RazorPage.EF.CRUD.Data.Entities
{
    public class Gadgets
    {
        public int Id { get; set; }
        public string ProductName { get; set; }
        public string Brand { get; set; }
        public decimal Cost { get; set; }
        public string Type { get; set; }
    }
}
In EF Core DbContext is like a database that manages all POCO classes(classes represent tables). Inside the 'Data' folder create a context class.
Data/MyWorldDbContext.cs:
using Dotnet5.RazorPage.EF.CRUD.Data.Entities;
using Microsoft.EntityFrameworkCore;

namespace Dotnet5.RazorPage.EF.CRUD.Data
{
    public class MyWorldDbContext : DbContext
    {
        public MyWorldDbContext(DbContextOptions<MyWorldDbContext> options) : base(options)
        {

        }
        public DbSet<Gadgets> Gadgets { get; set; }
    }
}
Add database connection string into 'appsetting.Development.json'
appsetting.Development.json:
"ConnectionStrings":{
    "MyWorldDbConnection":"your_connection"
}
Register 'MyWorlDbContext' into the dependency services.
Startup.cs:
services.AddDbContext<MyWorldDbContext>(options =>
{
	options.UseSqlServer(Configuration.GetConnectionString("MyWorldDbConnection"));
});

Read Operation:

Create a folder 'Gadgets' inside of the 'Pages' folder and then add razor page like 'Gadget.cshtml'(view) and 'Gadget.cshtml.cs'(model).
Pages/Gadgets/Gadget.cshtml.cs:
using System.Collections.Generic;
using System.Linq;
using System.Threading.Tasks;
using Dotnet5.RazorPage.EF.CRUD.Data;
using Microsoft.AspNetCore.Mvc.RazorPages;
using Microsoft.EntityFrameworkCore;

namespace Dotnet5.RazorPage.EF.CRUD.Pages.Gadgets
{
    public class GadgetModel : PageModel
    {
        public List<Data.Entities.Gadgets> AllGadgets = new List<Data.Entities.Gadgets>();

        private readonly MyWorldDbContext _myWorldDbContext;
        public GadgetModel(MyWorldDbContext myWorldDbContext)
        {
            _myWorldDbContext = myWorldDbContext;
        }

        public async Task OnGetAsync()
        {
            AllGadgets = await _myWorldDbContext.Gadgets.OrderByDescending(_ => _.Id).ToListAsync();
        }
    }
}
  • (Line: 10) To make our class file as a razor page model it needs to inherit 'Microsoft.AspNetCore.Mvc.RazorPages.PageModel'.
  • (Line: 12) Declare variable 'AllGadgets' which will be used to store the data from the database and this variable will be used in the 'Gadget.cshtml'(view) file for data binding.
  • (Line: 14-18) Injected the database context.
  • (Line: 20-23) The default method executed for the razor page HTTP Get request is 'OnGet' or 'OnGetAsync'. It is always ideal to have one get method in razor pages. If you want to customize the name of the HTTP Get request method then it should be like 'OnGet{YourCustomName}' or 'OnGet{YourCustomName}Async', but if we customize the method name then we have to specify the custom name as a value to the query parameter 'handler'. So don't give the custom name unless it is required. Inside of our 'OnGetAsync' method we need to write our logic to fetch the data from the database.
Pages/Gadgets/Gadgets.cshtml:
@page "/all-gadgets"
@model GadgetModel
<div>
    <table class="table table-dark table-striped">
        <thead>
            <tr>
                <th scope="col">Id</th>
                <th scope="col">Product Name</th>
                <th scope="col">Brand</th>
                <th scope="col">Cost</th>
                <th scope="col">Type</th>
            </tr>
        </thead>
        <tbody>
            @foreach (var item in Model.AllGadgets)
            {
                <tr>
                    <th scope="row">@item.Id</th>
                    <td>@item.ProductName</td>
                    <td>@item.Brand</td>
                    <td>@item.Cost</td>
                    <td>@item.Type</td>
                </tr>
            }
        </tbody>
    </table>
</div>
  • (Line: 1) The '@page' directive used for configuring the route.
  • (Line: 2) Define the 'Model' object.
  • (Line: 15-24) Looping the data to bind to the table.
Now run the application and access the route "https://localhost:5001/all-gadgets"

Create Operation:

In 'Pages/Gadgets' folder create new razor pages for creation like 'CreateGadget.cshtml'(view) and 'CreateGadget.cshtml.cs'(model).
Pages/Gadgets/CreateGadget.cshtml.cs:
using System.Threading.Tasks;
using Dotnet5.RazorPage.EF.CRUD.Data;
using Microsoft.AspNetCore.Mvc;
using Microsoft.AspNetCore.Mvc.RazorPages;

namespace Dotnet5.RazorPage.EF.CRUD.Pages.Gadgets
{
    public class CreateGadgetModel : PageModel
    {
        [BindProperty]
        public Data.Entities.Gadgets NewGadget { get; set; }
        private readonly MyWorldDbContext _myWorldDbContext;
        public CreateGadgetModel(MyWorldDbContext myWorldDbContext)
        {
            _myWorldDbContext = myWorldDbContext;
        }

        public IActionResult OnGetAsync()
        {
            return Page();
        }

        public async Task<IActionResult> OnPostAsync()
        {
            _myWorldDbContext.Gadgets.Add(NewGadget);
            await _myWorldDbContext.SaveChangesAsync();
            return Redirect("all-gadgets");
        }
    }
}
  • (Line: 10-11) The 'NewGadget' property decorated with the 'BindProperty' attribute, so this attribute will read the form posted data and store into the property.
  • (Line: 18-21) The 'OnGetAsync' method invoked for HTTP Get request, it just renders the page.
  • (Line: 23-28) The 'OnPostAsync' method invokes the HTTP post request, which means this will technically get invoked on a form post. So we know the 'BindProperty' attribute helps the property to store the form data, so we can save that to the database.
Pages/Gadgets/CreateGadget.cshtml:
@page "/creategadget"
@model CreateGadgetModel

<div>
    <form method="POST">
        <div class="mb-3">
            <label for="txtProductName" class="form-label">Product Name</label>
            <input asp-for="NewGadget.ProductName" type="text" class="form-control" id="txtProductName" >
        </div>
        <div class="mb-3">
            <label for="txtBrand" class="form-label">Brand</label>
            <input asp-for="NewGadget.Brand" type="text" class="form-control" id="txtBrand">
        </div>
        <div class="mb-3">
            <label for="txtCost" class="form-label">Cost</label>
            <input asp-for="NewGadget.Cost" type="text" class="form-control" id="txtCost">
        </div>
        <div class="mb-3">
            <label for="txtType" class="form-label">Type</label>
            <input asp-for="NewGadget.Type" type="text" class="form-control" id="txtType">
        </div>
        <button type="submit" class="btn btn-primary">Submit</button>
    </form>
</div>
  • Here on every input filed we used binded 'asp-for' razor HTML attribute, this makes form to load the data on submission. The 'asp-for' value must be our 'NewGadget' type properties.
Now in 'Gadget.cshtml' page add button that will navigate to the 'CreateGadget.cshtml' page.
Pages/Gadgets/Gadget.cshtml:
@page "/all-gadgets"
@model GadgetModel
<!-- Code hidden for display purpose -->
<div>
    <a asp-page="./creategadget" class="btn btn-primary">Create New Gadget</a>
    <table class="table table-dark table-striped">
       
    </table>
</div>
  • (Line: 5) Add a button that going to navigate to the 'CreateGadgets.cshtml' page. Here used 'asp-page'  razor attribute for defining our route.
step1:

step2:
step3:

Update Operation:

In the 'Pages/Gagets' folder create pages like 'EditGadget.cshtml' and 'EditGadget.cshtml.cs' for update operation.
Pages/Gadget/EditGadget.cshtml.cs:
using System.Linq;
using System.Threading.Tasks;
using Dotnet5.RazorPage.EF.CRUD.Data;
using Microsoft.AspNetCore.Mvc;
using Microsoft.AspNetCore.Mvc.RazorPages;
using Microsoft.EntityFrameworkCore;

namespace Dotnet5.RazorPage.EF.CRUD.Pages.Gadgets
{
    public class EditGadgetModel : PageModel
    {
        [BindProperty]
        public Data.Entities.Gadgets GadgetToUpdate { get; set; }

        private readonly MyWorldDbContext _myWorldDbContext;
        public EditGadgetModel(MyWorldDbContext myWorldDbContext)
        {
            _myWorldDbContext = myWorldDbContext;
        }

        public async Task<IActionResult> OnGetAsync(int id)
        {
            GadgetToUpdate = await _myWorldDbContext.Gadgets.Where(_ => _.Id == id).FirstOrDefaultAsync();
            if (GadgetToUpdate == null)
            {
                return Redirect("~/all-gadgets");
            }

            return Page();
        }

        public async Task<IActionResult> OnPostAsync()
        {
            _myWorldDbContext.Attach(GadgetToUpdate).State = EntityState.Modified;
            await _myWorldDbContext.SaveChangesAsync();
            return Redirect("~/all-gadgets");
        }
    }
}
  • (Line: 21-30) The 'OnGetAsync' method reads the 'id' value from the route. So from this, we can determine that HTTP request methods can read the route values as their input parameters. So based on 'id' value we will fetch records from the database.
  • (Line: 32-37) The 'OnPostAsync' method updating the data to the database.
Pages/Gadgets/EditGadget.cshtml:
@page "/edit/{id:int}"
@model EditGadgetModel

<div>
    <form method="POST">
         <input asp-for="GadgetToUpdate.Id" type="hidden" class="form-control" id="txtProductName" >
        <div class="mb-3">
            <label for="txtProductName" class="form-label">Product Name</label>
            <input asp-for="GadgetToUpdate.ProductName" type="text" class="form-control" id="txtProductName" >
        </div>
        <div class="mb-3">
            <label for="txtBrand" class="form-label">Brand</label>
            <input asp-for="GadgetToUpdate.Brand" type="text" class="form-control" id="txtBrand">
        </div>
        <div class="mb-3">
            <label for="txtCost" class="form-label">Cost</label>
            <input asp-for="GadgetToUpdate.Cost" type="text" class="form-control" id="txtCost">
        </div>
        <div class="mb-3">
            <label for="txtType" class="form-label">Type</label>
            <input asp-for="GadgetToUpdate.Type" type="text" class="form-control" id="txtType">
        </div>
        <button type="submit" class="btn btn-primary">Submit</button>
    </form>
</div>
  • Here 'EditGadget.cshtml' Html code almost the same as Html code in 'CreateGadget.cshtml', the only difference is we will store the record primary value as a hidden field.
Now add the edit button for each record in the table in the 'Gadget.cshtml' page.
Pages/Gadgets/Gadget.cshtml:
@page "/all-gadgets"
@model GadgetModel
<!-- code hidden for display purpose -->
<div>
    <a asp-page="./creategadget" class="btn btn-primary">Create New Gadget</a>
    <table class="table table-dark table-striped">
        <thead>
            <tr>
                <th scope="col">Actions</th>
            </tr>
        </thead>
        <tbody>
            @foreach (var item in Model.AllGadgets)
            {
                <tr>
                    <td>
                        <a  href='@($"/edit/{item.Id}")' class="btn btn-primary">Edit</a> |
                    </td>
                </tr>
            }
        </tbody>
    </table>
</div>
  • (Line: 9) Added new column like 'Actions'.
  • (Line: 7) Edit button for respective record of the table.
step1:
step2:
step:3

Delete Operation:

Now for the delete operation, we will implement an HTTP post method inside of the 'Gadget.cshmtl.cs' file. So instead of using 'OnPostAsync' as the method name, we will customize the method name as 'OnPostDeleteAsync'.
Pages/Gadgets/Gadgets.cshtml.cs:
namespace Dotnet5.RazorPage.EF.CRUD.Pages.Gadgets
{
    public class GadgetModel : PageModel
    {
		// code hidden for displya purpose
        public async Task<IActionResult> OnPostDeleteAsync(int id)
        {
            var currentGadget = await _myWorldDbContext.Gadgets.FindAsync(id);
            if (currentGadget != null)
            {
                _myWorldDbContext.Gadgets.Remove(currentGadget);
                await _myWorldDbContext.SaveChangesAsync();
            }
            return Redirect("~/all-gadgets");
        }
    }
}
  • This method get executed for a HTTP post-call and URL should be like 'http:yourdomain/all-gadgets?id={idvalue}&handler=delete'. Inside of this method implementing logic to delete the recorded from the database.
Pages/Gadgets/Gadget.cshtml:
@page "/all-gadgets"
@model GadgetModel
<!-- code hidden for display purpose -->
<div>
    <a asp-page="./creategadget" class="btn btn-primary">Create New Gadget</a>
    <table class="table table-dark table-striped">
       
        <tbody>
            @foreach (var item in Model.AllGadgets)
            {
                <tr>
                    <td>
                        <a href='@($"/edit/{item.Id}")' class="btn btn-primary">Edit</a> |
                        <button type="button" onclick="deleteGadget(@item.Id)" class="btn btn-primary">delete
                        </button>

                    </td>
                </tr>
            }
        </tbody>
    </table>
</div>

<div class="modal fade" id="deleteGadgetModal" tabindex="-1" aria-labelledby="exampleModalLabel" aria-hidden="true">
    <div class="modal-dialog">
        <div class="modal-content">
           
            <div class="modal-body">
                <h4>Are you sure, you want to delete?</h4>
            </div>
            <div class="modal-footer">
                <button type="button" class="btn btn-secondary" onclick="closeModal()" data-bs-dismiss="modal">Close</button>
                <form method="POST" id="confirmDelete">
                    <button type="submit"  class="btn btn-primary">delete</button>
                </form>
            </div>
        </div>
    </div>
</div>
  • (Line: 14-15) Added the 'Delete' button. Delete button registered with a click event method like 'deleteGadget()'.
  • (Line: 24-39) Add the Html for bootstrap 'Modal'.
  • (Line: 32) Added operation cancel button, registered with a click event method like 'closeModal()'.
  • (Line: 33-35) Confirm delete button enclosed in a form, so that on clicking button post-operation will be activated.
Now let's add some javascript code for interacting with Bootstrap Modal.
wwwroot/js/site.js:
function deleteGadget(id) {
  url = "/all-gadgets?id=" + id + "&handler=delete";
  var deleteFormEl = document.getElementById("confirmDelete");
  deleteFormEl.setAttribute("action", url);
  $("#deleteGadgetModal").modal("show");
}

function closeModal() {
  $("#deleteGadgetModal").modal("hide");
}
  • The 'deleteGadget(id)' method prepares the delete post URL and binds the URL to a form on the Bootstrap Modal.
  • The 'closeModal' method to close the BootstrapModal.
So that's all about the .Net5 Razor Pages CRUD operations with entity framework core.

Video Session:

Support Me!
Buy Me A Coffee PayPal Me

Wrapping Up:

Hopefully, I think this article delivered some useful information on .Net5 Razor Pages CRUD operation with the entity framework. I love to have your feedback, suggestions, and better techniques in the comment section below.

Refer:

Follow Me:

Comments

  1. Love your tutorial! Hope you can post how to put more entities and related entities.
    Thanks for sharing!

    ReplyDelete

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