Skip to main content

A Sample On .Net Core Web API Using Dapper


Overview On Dapper Object-Relational Mapping:

Dapper is an Object-Relational Mapping framework for .Net applications. It is a mapping model between the database and .Net objects. The Dapper provides all query and command execution methods as extension methods under the 'System.Data.IDbConnection' interface. The Dapper works as a similar ADO.Net but with much more model mapping support. The Dapper key features are like:
  • High performance in query execution
  • Multiple query execution support
  • An easy model mapping between the .Net Object and database result.

Create A Sample .Net Core Web API Application:

Let's understand the Dapper ORM query and commands execution steps by writing some sample code, so let's get started by creating a .Net Core Web API application. The IDE's for development can be chosen by personal preference but the most recommended IDE's are Visual Studio 2019 and Visual Studio Code.

SQL Table Schema:

In this article we are going to work on 'Todo' table, so execute the below table schema.
CREATE TABLE [dbo].[Todo] (
    [Id]  INT  IDENTITY (1, 1) NOT NULL,
    [ItemName] VARCHAR (MAX) NULL,
    [IsCompleted] BIT NOT NULL
);
Now run the sample test data.
SET IDENTITY_INSERT [dbo].[Todo] ON
INSERT INTO [dbo].[Todo] ([Id], [ItemName], [IsCompleted]) VALUES (1, N'Buy a book', 1)
INSERT INTO [dbo].[Todo] ([Id], [ItemName], [IsCompleted]) VALUES (2, N'Need To Watch Movie', 0)
INSERT INTO [dbo].[Todo] ([Id], [ItemName], [IsCompleted]) VALUES (3, N'Book A Flight Ticke', 0)
SET IDENTITY_INSERT [dbo].[Todo] OFF

Install Packages:

SQL Provider Package:

Install-Package System.Data.SqlClient
Dapper Package:

Install-Package Dapper

Initial Project Configuration Steps(Connection String / Models / Repositories):

In this section we are going to implement initial steps like adding ConnectionString, Models, Repositories with some basic configurations.

In appsettings.development.json file add your SQL connection string as below.
{
  "Logging": {
  },
  "AllowedHosts": "*",
  "ConnectionStrings": {
    "MyWorldDbConnection": "your_sql_server_connection"
  }
}
Now add Todo.cs model
Models/Todo.cs:
namespace API.Dapper.Sample.Models
{
    public class Todo
    {
        public int Id { get; set; }
        public string ItemName { get; set; }
        public bool IsCompleted { get; set; }
    }
}
Now let's create 'Todo' repository and it interface.
Repos/ITodoRepository.cs:
using API.Dapper.Sample.Models;
using System.Collections.Generic;
using System.Threading.Tasks;

namespace API.Dapper.Sample.Repos
{
    public interface ITodosRepository
    {
        
    }
}
  • Here we have added few references(libraries accessed with using statement) intentionally because all these references are required by us on completion of the sample.
Repos/TodoRepository.cs:
using API.Dapper.Sample.Models;
using Dapper;
using Microsoft.Extensions.Configuration;
using System.Collections.Generic;
using System.Data;
using System.Data.SqlClient;
using System.Linq;
using System.Threading.Tasks;

namespace API.Dapper.Sample.Repos
{
    public class TodosRepository: ITodosRepository
    {
        private string myWorldDbConnection = string.Empty;

        private IDbConnection Connection
        {
            get
            {
                return new SqlConnection(myWorldDbConnection);
            }
        }
        public TodosRepository(IConfiguration configuration)
        {
            myWorldDbConnection = configuration.GetConnectionString("MyWorldDbConnection");
        }
    }
}
  • (Line: 25) The 'Microsoft.Extensions.Configuration.IConfiguration' is injected into the 'TodosRepository'. The 'IConfiguration' interface has the capability to access the appsettings. The 'GetConnectionString()' is default method in 'IConfiguration' which can read the 'ConnectionStrings' property object in the appsettings.
  • (Line: 16-22) The 'Connection' property of type 'System.Data.IDbConnection' initialized. This property uses 'System.Data.SqlClient.SqlConnection' instance to open the database connection.
Now register the 'TodosRepository' in DI(dependency injection) service in the startup file
Startup.cs:
public void ConfigureServices(IServiceCollection services)
{
	services.AddControllers();
	services.AddScoped<ITodosRepository, TodosRepository>();
}
Let's now add a 'TodosController' as follow
Controllers/TodosController.cs:
using API.Dapper.Sample.Models;
using API.Dapper.Sample.Repos;
using Microsoft.AspNetCore.Mvc;
using System.Threading.Tasks;

namespace API.Dapper.Sample.Controllers
{
    [Route("api/[controller]")]
    [ApiController]
    public class TodosController : ControllerBase
    {
        private readonly ITodosRepository _todosRepository;
        public TodosController(ITodosRepository todosRepository)
        {
            _todosRepository = todosRepository;
        }
    }
}
  • (Line: 13) Injects 'ITodosRepository'

Read Collection Of Records:

Using Dapper ORM query extension methods we need to fetch collection records from the database.

Now create an abstract method in the 'ITodosRepository.cs' that represents a method that outputs the collection of records.
Repos/ITodosRepository.cs:
Task<List<Todo>> GetAllTodosAsync();
Now implement this abstract method in the 'TodosRepository.cs'
Repos/TodosRepository.cs:
public async Task<List<Todo>> GetAllTodosAsync()
{
	using(IDbConnection conn = Connection)
	{
		string query = "SELECT * FROM Todo";
		List<Todo> todos = (await conn.QueryAsync<Todo>(sql: query)).ToList();
		return todos;
	}
}
  • (Line: 3) The 'using' statement automatically closes the database connection string once the scope of the code executes out the 'using' statement.
  • (Line: 5) The simple raw SQL query to fetch all records.
  • (Line: 6) The 'Dapper.SqlMapper..QueryAsync<T>()' method which we using as extension method of 'System.Data.IDbConnection'. The QueryAsync method executes the query which takes it as an input parameter and returns the data by mapping to the 'T' type defined to it.
Now define the action method endpoint.
Controllers/TodosController.cs:
[HttpGet]
[Route("get-all")]
public async Task<IActionResult> GetAllTodosAsync()
{
	var result = await _todosRepository.GetAllTodosAsync();
	return Ok(result);
}

Read Single Record:

Let's define an abstract method in 'ITodosRepository', this method going to fulfill the role to return a single record from our repository.
Repos/ITodosRepository.cs:
Task<Todo> GetTodoByIdAsync(int id);
Now let's implement this abstract method into our 'TodosRepository'
Repos/TodosRepository.cs:
public async Task<Todo> GetTodoByIdAsync(int id)
{
	using(IDbConnection conn = Connection)
	{
		string query = "SELECT * FROM Todo WHERE Id = @id";
		Todo todo = await conn.QueryFirstOrDefaultAsync<Todo>(sql: query, param: new { id });
		return todo;
	}
}
  • (Line: 5) Now the raw SQL query contains parameter '@id', dapper will pass the value at the time query execution.
  • (Line: 6) The extension method 'QueryFirstOrDefaultAsync' returns the first record as per the filter we passed. To this extension method, we are passing filter values as anonymous objects using the 'new' keyword.
Now define the action method endpoint
Controllers/TodosController.cs:
[HttpGet]
[Route("get-todoitem-by-id")]
public async Task<IActionResult> GetTodoItemByIdAsync(int id)
{
	var result = await _todosRepository.GetTodoByIdAsync(id);
	return Ok(result);
}

Read Multiple Result Sets:

The Dapper has the capability to return the multiple table results sets. Now let's create a new model to capture multiple results.
Models/TodosContainer.cs:
using System.Collections.Generic;

namespace API.Dapper.Sample.Models
{
    public class TodosContainer
    {
        public int Count { get; set; }
        public List<Todo> Todos {get;set;}
    }
}
  • Here we have 2 properties one for the total count and the other for the list of 'Todos'.
Now let's define an abstract method for reading multiple results in 'ITodosRepository'
Repos/ITodosRepository.cs:
Task<TodosContainer> GetTodosAndCountAsync();
Now let's write an implementation for this abstract method
Repos/TodosRepository.cs:
public async Task<TodosContainer> GetTodosAndCountAsync()
{
	using (IDbConnection conn = Connection)
	{
		string query = @"
				SELECT COUNT(*) FROM Todo

	
				SELECT * FROM Todo";

		var reader = await conn.QueryMultipleAsync(sql: query);

		return new TodosContainer
		{
			Count = (await reader.ReadAsync<int>()).FirstOrDefault(),
			Todos = (await reader.ReadAsync<Todo>()).ToList()
		};
	}
}
  • (Line: 5-9) Here defined to queries one returns count of todos and other returns total todos(If you want you can return select query of fetching data of two tables also).
  • (Line: 11) The extension method 'QueryMultipleAsync' executes the query and returns multiple result sets.
  • (Line: 15) Reading the first result set i.e total count.
  • (Line: 16) Reading the second result set i.e collection of 'Todos'.
Now let's define the action method endpoint.
Controllers/TodosController.cs:
[HttpGet]
[Route("get-todos-and-count")]
public async Task<IActionResult> GetTodosAndCountAsync()
{
	var result = await _todosRepository.GetTodosAndCountAsync();
	return Ok(result);
}

Save Record:

Repos/ITodosRepository.cs:
Task<int> SaveAsync(Todo newTodo);
Repos/TodosRepository.cs:
public async Task<int> SaveAsync(Todo newTodo)
{
	using(IDbConnection conn = Connection)
	{
		string command = @"
				INSERT INTO Todo(ItemName, IsCompleted)
				VALUES(@ItemName, @IsCompleted)";

		var result = await conn.ExecuteAsync(sql: command, param: newTodo);
		return result;
	}
}
  • (Line: 6-7) Here we can see SQL insert command and with dynamic parameters like '@ItemName','@IsCompleted'.
  • (Line: 9) The extension method 'ExecuteAsync' executes the given command to it. This method takes 'param' as 'newTodo'(Todo instance), each property name of 'newTodo' must match with the dynamic parameter name is the SQL command. The return type of the 'ExecuteAsync' is an integer value to represent the number of rows was effected on command execution, so if it returns zero then there is no effect of the command on the database.
Now let's define the action method endpoint.
Controllers/TodosController.cs:
[HttpPost]
[Route("save")]
public async Task<IActionResult> SaveAsync(Todo newTodo)
{
	var result = await _todosRepository.SaveAsync(newTodo);
	return Ok(result);
}

Update Record:

Repos/ITodosRepository:
Task<int> UpdateTodoStatusAsync(Todo updateTodo);
Repos/TodosRepository:
public async Task<int> UpdateTodoStatusAsync(Todo updateTodo)
{
	using(IDbConnection conn = Connection)
	{
		string command = @"
		UPDATE Todo SET IsCompleted = @IsCompleted WHERE Id = @Id";

		var result = await conn.ExecuteAsync(sql: command, param: updateTodo);
		return result;
	}
}
  • Here we are updating only the 'IsCompleted' column of the Todo table
Controllers/TodosController.cs:
[HttpPost]
[Route("update-todo-status")]
public async Task<IActionResult> UpdateTodoStatusAsync(Todo updateTodo)
{
	var result = await _todosRepository.UpdateTodoStatusAsync(updateTodo);
	return Ok(result);
}

Delete Record:

Repos/ITodosRepository:
Task<int> DeleteAsync(int id);
Repos/TodosRepository:
public async Task<int> DeleteAsync(int id)
{
	using(IDbConnection conn = Connection)
	{
		string command = @"DELETE FROM Todo WHERE Id = @id";
		var result = await conn.ExecuteAsync(sql: command, param: new { id });
		return result;
	}
}
  • Here we can observe SQL raw delete query based on the '@id' parameter
Controllers/TodoController.cs:
[HttpDelete]
[Route("delete")]
public async Task<IActionResult> DeleteAsync(int id)
{
	var result = await _todosRepository.DeleteAsync(id);
	return Ok(result);
}

Wrapping Up:

Hopefully, I think this article delivered some useful information on the Dapper ORM integration in .Net Core Application. I love to have your feedback, suggestions, and better techniques in the comment section below.

Follow Me:

Comments

Popular posts from this blog

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", defaults:new { …

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.Types likely to be called Grap…

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 VersioningUrl Path VersioningMedia 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.AspNetCore.Mvc.Versioning -version 4.0.0 Register API V…

.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 from the client, then the entire …

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: PickerControllerPickerOptions 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", "Lion", "Elephant"…

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 below.
PersonController.cs: us…

Blazor WebAssembly Dynamic Form Validation

Introduction: In Blazor WebAssembly(client-side framework) form validation can be done with Data Annotations. Using Data Annotations we can validate form either by default validation attributes or by creating custom validation attributes. Using this Data Annotation attribute we can dynamically add or remove validation on a specific field in a form.
Create Blazor WebAssembly Project: To create a Blazor WebAssembly template project need to install the latest version of VisualStudio 2019 for rich intelligence support or we can use VisualStudio code but less intelligence support from the editor. Click here to know about Blazor WebAssembly template creation. Blazor WebAssembly is in preview mode, not yet ready for production.
Create Razor Component: After creating a sample project using the Blazor WebAssembly template, in "Pages" folder add new Razor Component, name it as "UserForm.razor"
Add Route: In Blazor routing can be configured using @page  directive, and URL should b…

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 information or changed …

NestJS API CRUD Operations With MongoDB

Introduction: NestJS is a framework used to develop server-side applications. NestJS built on top of Node.js frameworks like Express. It is a combination of Progressive Javascript, Object-Oriented Programming, Functional Programming, and Functional Reactive Programming.
Nest CLI Installation: Using Nest CLI we are able to generate the NestJS starter project with the default template. To install Nest CLI globally over our system open command prompt and run the command
npm i -g @nestjs/cli Now create a sample project by using Nest CLI command  nest new your_project_name package.json: Now open the package.json file from the sample application created, you can observe few properties like "scripts", "dependencies", and "devDependencies".
"dependencies" contains all plugins to be installed and used them to run the application.
"devDependencies" contain all plugins to be installed and used them at the time of application development.
"scrip…

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-ControlPragmaVary 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 fresh response from serverno-store…