Skip to main content

.NET5 MVC CRUD Operations Using Entity Framework Core

In this article, we will learn about .Net5 MVC CRUD operation using Entity Framework Core.

MVC:

The Model-View-Controller(MVC) is an architectural pattern. MVC divides UI applications into 3 different layers. Each layer will have its own responsibility.

An MVC application on encountering the user request will be sent to the controller. The controller will query the required data from the database and then furnished our data into 'Model' and then select appropriate 'View'. The 'View' will render the data or logic inside of the 'Model'. The 'Model' is the bridge between 'Controller' and 'View' for transferring the data. So in  MVC, the 'Controller' depends on both 'Model' and 'View', the 'View' depends on 'Model'.

Create A .Net5 MVC Application:

Begin our journey by creating a .Net5 MVC application.

Visual Studio users can easily create a .Net5 MVC templated application. On Creating application Visual Studio UI shows different template options in that we have to select "ASP .NET Core Web App(model - view -controller)".

Here for this demo, I'm using Visual Studio Code Editor and .NET CLI. Run the below .NET CLI command to create .Net5 MVC application.
CLI Command To MVC Application:
dotnet new mvc -n your_project_name
After creating a project, we need to aware of few basic things like:

MVC DI(Dependency Injection) Service - To enable MVC related services with DI in 'Startup.cs' we need to register 'AddControllersWithViews'

Endpoint Middleware - MVC supports 2 different approaches of routing like 'Conventional Based Routing' and 'Attribute-Based Routing'. So in the endpoint middleware by default configures with conventional based routing on creating the project.

_ViewImports.cshtml - File used to configure namespaces.

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

Shared/_Layout.cshtml - Default master layout.

wwwroot - Folder to store static files like 'js', 'css', '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]

Set Up 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.MVC.CRUD.EF.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.MVC.CRUD.EF.Data.Entities;
using Microsoft.EntityFrameworkCore;

namespace Dotnet5.MVC.CRUD.EF.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'.
appsettings.Development.json:
"ConnectionStrings":{
    "MyWorldDbConnection":"your_connection"
}
Register 'MyWorlDbContext' into the dependency services.
services.AddDbContext<MyWorldDbContext>(options =>
{
	options.UseSqlServer(Configuration.GetConnectionString("MyWorldDbConnection"));
});

Read Operation:

First, let's create a 'Model' class for our read operation.
Models/GadgetsContainerVm.cs:
using System.Collections.Generic;
using Dotnet5.MVC.CRUD.EF.Data.Entities;

namespace Dotnet5.MVC.CRUD.EF.Models
{
    public class GadgetsContainerVm
    {
        public List<Gadgets> AllGadgets { get; set; }
    }
}
Now in the 'Controllers' folder add a new controller like 'GadgetsController.cs'. Now for our read operation let's add a new action method and name it like 'All'. So our action method contains logic to fetch the data from the database and then pass data to  'Model' and then invoke appropriate 'View'.
Controllers/GadgetsController.cs:
using System.Linq;
using System.Threading.Tasks;
using Dotnet5.MVC.CRUD.EF.Data;
using Dotnet5.MVC.CRUD.EF.Models;
using Microsoft.AspNetCore.Mvc;
using Microsoft.EntityFrameworkCore;

namespace Dotnet5.MVC.CRUD.EF.Controllers
{
    public class GadgetsController : Controller
    {
        private readonly MyWorldDbContext _myWorldDbContext;
        public GadgetsController(MyWorldDbContext myWorldDbContext)
        {
            _myWorldDbContext = myWorldDbContext;
        }

        [HttpGet]
        public async Task<IActionResult> All()
        {
            var allGadtets = await _myWorldDbContext.Gadgets.OrderByDescending(_ => _.Id).ToListAsync();
            var model = new GadgetsContainerVm
            {
                AllGadgets = allGadtets
            };
            return View("Index",model);
        }
    }
}
  • (Line: 10) To make a class as a controller it should inherit 'Microsoft.AspNetCore.Mvc.Controller'.
  • (Line: 12-16) Injecting our database context.
  • (Line: 18) Action method decorated with 'HttpGet'. That HTTP verb represents the type of request that can invoke our action method.
  • (Line: 19-27) Fetching data from the database and then saving it into the 'Model' object. Finally, invoke the 'View' by sending 'Model' data.
Now let's create our 'View'. In the 'Views' folder create a new folder like 'Gadgets'(this folder name must be matched with our controller name so that controller can check the view in that folder). Now add 'Index.cshtml'(View) in 'Gadgets' folder.
Views/Gadgets/Index.cshtml:
@model GadgetsContainerVm
<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) Need to define our model using '@model'
  • (Line: 14) Looping all our data to bind as table rows
Now let's access our route "https://localhost:5001/gadgets/all".

Create Operation:

Let's create an action method for 'Create Operation' of HTTP Get request.
Controllers/GadgetsController.cs:
[HttpGet]
public IActionResult Create()
{
	return View("Create");
}
  • Simple HTTP Get request action method that return the view(eg: "Create.cshtml").
Now let's create an HTTP Post request action method for our 'Create Operation'.
Controllers/GadgetsController.cs:
[HttpPost]
[ValidateAntiForgeryToken]
public async Task<IActionResult> Create(Gadgets model)
{
	_myWorldDbContext.Gadgets.Add(model);
	await _myWorldDbContext.SaveChangesAsync();
	return RedirectToAction("All");
}
  • (Line: 1) Decorated with the 'HttpPost' attribute to specify the type HTTP request can invoke the action method.
  • (Line: 2) Decorated with the 'ValidateAntiForgeryToken' to protect the form posted data.
  • (Line: 3) Our overloaded 'Create' action method takes the 'Gadgets' type as an input parameter. So on form post, all form data will be stored into this parameter.
  • (Line: 4-6) Saving the new record into the database. After saving we will navigate users to 'All' action method
Now create 'Create.cshtml' view file in the folder 'Views/Gadgets'.
Views/Gadgets/Create.cshtml:
@model Dotnet5.MVC.CRUD.EF.Data.Entities.Gadgets

<div>
    <form aps-action="create" method="post">
        <div class="mb-3">
            <label for="txtProductName" class="form-label">Product Name</label>
            <input asp-for="ProductName" type="text" class="form-control" id="txtProductName" >
        </div>
        <div class="mb-3">
            <label for="txtBrand" class="form-label">Brand</label>
            <input asp-for="Brand" type="text" class="form-control" id="txtBrand" >
        </div>
        <div class="mb-3">
            <label for="txtCost" class="form-label">Cost</label>
            <input asp-for="Cost" type="text" class="form-control" id="txtCost" >
        </div>
        <div class="mb-3">
            <label for="txtType" class="form-label">Type</label>
            <input asp-for="Type" type="text" class="form-control" id="txtType" >
        </div>
        
        <button type="submit" class="btn btn-primary">Submit</button>
    </form>
</div>
  • (Line: 1) Defined 'Model' type.
  • (Line: 4) The 'asp-action' attribute to specify the action name as its value. We also need to configure the 'method' attribute and its value should be 'post'.
  • All input fields in the form decorated with 'asp-for' attribute. So 'asp-for' attribute value must match with the properties of the 'Gadget' type.
Now add the button in  'Views/Gadgets/Index.cshtml' that will navigate to our 'Create' page.
Views/Gadgets/Index.csthml
@model GadgetsContainerVm
<!-- Code hidden for display purpose -->
<div>
    <a href="/gadgets/create" class="btn btn-primary">Create</a>
    <table class="table table-dark table-striped">
    </table>
</div>
step:1
step2:
step:3

Update Operation:

Now let's create the 'Update Operation' action method for the HTTP GET request.
Controllers/GadgetsController.cs:
[HttpGet]
public async Task<IActionResult> Edit(int id)
{
	var gadget = await _myWorldDbContext.Gadgets.Where(_ => _.Id == id).FirstOrDefaultAsync();
	if (gadget == null)
	{
		return NotFound();
	}
	return View("Edit", gadget);
}
  • (Line: 2) Method input parameter 'id' will be read from the URL query parameter.
  • In this HTTP GET request method fetching the data to be edited.
Now let's create the 'Update Operation' action method for the HTTP POST request.
Controllers/GadgetController.cs:
[HttpPost]
[ValidateAntiForgeryToken]
public async Task<IActionResult> Edit(Gadgets modelToUpdate)
{
	_myWorldDbContext.Update(modelToUpdate);
	await _myWorldDbContext.SaveChangesAsync();
	return RedirectToAction("All");
}
  • (Line: 1) Decorated with 'HttpPost'.
  • (Line: 2) Decorated with 'ValidateAntiForgeryToken' attribute for protecting form data posting.
  • (Line: 3-8) Updating the form posted data to database and then redirecting to 'All' action method.
Now let's create our new  view 'Edit.cshtml'. Here 'Edit.cshtml' contains HTML similar to 'Create.cshtml' only difference like we need to maintain our record 'Id' value in hidden field.
Views/Gadgets/Edit.cshtml:
@model Dotnet5.MVC.CRUD.EF.Data.Entities.Gadgets

<div>
    <form aps-action="Edit" method="post">
        <h4>Update</h4>
        <input asp-for="Id" type="hidden" class="form-control" id="txtProductName" >
        <div class="mb-3">
            <label for="txtProductName" class="form-label">Product Name</label>
            <input asp-for="ProductName" type="text" class="form-control" id="txtProductName" >
        </div>
        <div class="mb-3">
            <label for="txtBrand" class="form-label">Brand</label>
            <input asp-for="Brand" type="text" class="form-control" id="txtBrand" >
        </div>
        <div class="mb-3">
            <label for="txtCost" class="form-label">Cost</label>
            <input asp-for="Cost" type="text" class="form-control" id="txtCost" >
        </div>
        <div class="mb-3">
            <label for="txtType" class="form-label">Type</label>
            <input asp-for="Type" type="text" class="form-control" id="txtType" >
        </div>
        
        <button type="submit" class="btn btn-primary">Submit</button>
    </form>
</div>
  • (Line: 6) Hiden field to store our 'Id' value.
Now add the edit button for each record in the table of 'Index.cshtml'
@model GadgetsContainerVm
<!-- Code hidden for display purpose -->
<div>
    <a href="/gadgets/create" class="btn btn-primary">Create</a>
    <table class="table table-dark table-striped">
       
        <tbody>
            @foreach (var item in Model.AllGadgets)
            {
                <tr>
                  
				  
                    <td>
                        <a class="btn btn-primary" href='@($"edit?id={@item.Id}")'>Edit</a>
                    </td>
                </tr>
            }
        </tbody>
    </table>
</div>
  • (Line: 14) Configure 'Edit' but with appropriate route.
step:1
step:2
step:3

Delete Operation:

Now let's create 'Delete' operation action method for HTTP POST request.
Controllers/GadgetsController.cs:
[HttpPost]
[ValidateAntiForgeryToken]
public async Task<IActionResult> Delete(int id)
{
	var gadgetToDelete = await _myWorldDbContext.Gadgets.Where(_ => _.Id == id).FirstOrDefaultAsync();
	if (gadgetToDelete != null)
	{
		_myWorldDbContext.Gadgets.Remove(gadgetToDelete);
		await _myWorldDbContext.SaveChangesAsync();
	}
	return RedirectToAction("All");
}
  • (Line: 1) Decorated with 'HttpPost' attribute.
  • (Line: 2) Decorated with 'ValidateAntiForgeryToken' to avoid forgery request.
  • (Line: 3-12) Based on query parameter 'id' value fetch the record form the database and then delete it from the database and finally navigate to 'All' action method.
In 'Index.cshtml', we need add 'Delete' button and need to configure Bootstrap Modal popup to display the delete confirmation.
Views/Gadgets/Index.csthml:
@model GadgetsContainerVm
<!-- Code hidden for display purpose -->
<div>
    <a href="/gadgets/create" class="btn btn-primary">Create</a>
    <table class="table table-dark table-striped">
        </thead>
        <tbody>
            @foreach (var item in Model.AllGadgets)
            {
                <tr>
                    <td>
                        <a class="btn btn-primary" href='@($"edit?id={@item.Id}")'>Edit</a>|
                        <button class="btn btn-danger" type="button" onclick="deleteGadget(@item.Id)">Delete</button>
                    </td>
                </tr>
            }
        </tbody>
    </table>
</div>

<div class="modal fade" id="deleteModal" tabindex="-1" aria-labelledby="exampleModalLabel" aria-hidden="true">
  <div class="modal-dialog">
    <div class="modal-content">

      <div class="modal-body">
        <h4>Are your sure, you want to delete?</h4>
      </div>
      <div class="modal-footer">
        <button type="button" class="btn btn-secondary" data-bs-dismiss="modal">Close</button>
        <form method="POST" id="deleteForm">
        <button type="submit" class="btn btn-primary">Delete</button>

        </form>
      </div>
    </div>
  </div>
</div>
  • (Line: 13) Added the 'Delete' button. It click event registered to a method 'deleteGadget'.
  • (Line: 21-37) Html code for Bootstrap Modal.
  • (Line: 31) Here delete button is to invoke our Http Post request 'Delete' action and this button need to be encapsulated with form tag to inoke the post request. The URL will be append to the 'Form' tag dynamically through javascript code(will be show in next step).
Now go to 'wwwroot/js/site.js' file and add the below script.
wwwroot/js/site.js:
function deleteGadget(id) {
    let url = "/gadgets/delete?id="+ id;
    let formElement = document.getElementById("deleteForm");
    formElement.setAttribute("action", url);
    $("#deleteModal").modal('show');
}
  • (Line: 2) Framing our HTTP Post request URL.
  • (Line: 3) Fetching the Form element. This is the form encapsulated our confirm 'Delete' button on bootsrap modal popup.
  • (Line: 4) Adding the 'action' attribute to 'Form' tag and it's value is URL we just framed.
  • (Line: 5) Opens the Bootstrap Modal popup.
So that's all about the .Net5 MVC application CRUD operations using 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 MVC application 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

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

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

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

.Net5 Web API Managing Files Using Azure Blob Storage

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

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

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

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

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

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