Skip to main content

Model Validation In Asp.Net Core Application Using Fluent Validation Library

In this article, we will explore the usage of the Fluent Validation library in the Asp.Net Core application.

Fluent Validation Library:

Fluent Validation is a popular .Net library for enabling validation rules. It has a lot of features like in-built validation rules that are most commonly used in any application and also has flexible support for creating custom rules. Implementing Fluent validation rules is a cleaner approach than using the 'DataAnnotation'(.Net default implementation for applying validation rules). It can be automatically injected into .NetCore model validations without any explicit implementation.

How To Implement Fluent Validation To A Model:

To apply fluent validation to the model, we have to create a separate validator class. The validator class must inherit from 'FluentValidation.AbstractValidator<TModel>'. Inside of the constructor need to apply required validation for the properties of 'TModel'.
public class Student
{
	public string Name { get; set; }
	public int Age { get; set; }
}

public class StudentValidator:AbstractValidator<Student>
{
	public StudentValidator()
	{
		RuleFor(_ => _.Name).NotNull();
		RuleFor(_ => _.Age).GreaterThan(10);
	}
}

Built-in Validators Of Fluent Validation Library:

The following are the build-in validators of the fluent validation library:
NotNull Validator
RuleFor(person => person.FirstName).NotNull()
NotEmpty Validator
RuleFor(person => person.FirstName).NotEmpty()
NotEqual Validator
RuleFor(person => person.Name).NotEqual("Naveen");

// can compare with another prop as well
RuleFor(person => person.Name).NotEqual(person => person.NickName);
Equal Validator
RuleFor(person => person.Name).Equal("naveen")

//compare with other props
RuleFor(person => person.Name).Equal(person => person.NickName)
Length Validator
RuleFor(person => person.Name).Length(1,50)
MaxLength Validator
RuleFor(person => person.Name).MaximumLength(100)
MinLength Validator
RuleFor(person => person.Name).MinimumLength(10)
Less Than Validator
RuleFor(person => person.Age).LessThan(20)

// less than another property
RuleFor(person => person.Age).LessThan(person => person.MaxAgeLimit)
Less Than Or Equal Validator
RuleFor(person => person.Age).LessThanOrEqualTo(20)

// less than or equals to other property
RuleFor(person => person.Age).LessThanOrEqualTo(person => person.MaxAgeLimit)
Greater Than Validator
RuleFor(person => person.Age).GreaterThan(5)

// Greater than other property value
RuleFor(person => person.Age).GreaterThan(person => person.MinimumAgetLimit)
Greater Than Or Equal Validator
RuleFor(person => person.Age).GreaterThanOrEqualTo(5)

// Greater than or equals to other property value
RuleFor(person => person.Age).GreaterThanOrEqualTo(person => person.MinimumAgetLimit)
Regular Expression Validator
RuleFor(person => person.Name).Matches("Regex pattern")
Email Validator
RuleFor(person => person.Email).EmailAddress()
Credit Card Validator
RuleFor(person => person.CreditCardNumber).CreditCard()
Null Validator
RuleFor(person => person.Name).Null()
ExclusiveBetween Validator
RuleFor(person => person.Rank).ExclusiveBetween(1,10)
InClusiveBetween Validator
RuleFor(person => person.Rank).InclusiveBetween(1,10)

Create A .Net5 MVC Application:

Fluent Validation library can be used in any of the Asp.Net Core Applications. In this demo, we are going to create a .Net5 MVC sample application.



Install Fluent Validation Library:

Package Manager Command:
Install-Package FluentValidation.AspNetCore -Version 10.3.3

.NET CLI Command:
dotnet add package FluentValidation.AspNetCore --version 10.3.3

Register Fluent Validation Service:

Now register the fluent validation service as an extension to the MVC service because of this service registration fluent validation gets integrated with MVC model validations.
Startup.cs:
services.AddControllersWithViews()
.AddFluentValidation(options =>
{
	options.RegisterValidatorsFromAssemblyContaining(typeof(Startup));
});
  • Here 'RegisterValidatorsFromAssemblyContaining' it will load all the validator entity of each modal automatically without configuring explicitly. So to this option, we just need to pass any class that is under the root namespace of the library(eg: 'Startup.cs' & 'Program.cs'), so that it can identify all validator classes in our project under that namespace. 

Implement Fluent Validation For Model:

Let's understand how to enable modal validation in Asp.Net Core using fluent validation. Let's create a view model like 'PersonViewModel.cs' in the 'Models' folder.
Models/PersonViewModel.cs:
namespace FluentValidationDemo.MVC.Models
{
    public class PersonViewModel
    {
        public int ID { get; set; }
        public string LastName { get; set; }
        public string FirstName { get; set; }
        public int Age { get; set; }
    }
}
Now our goal is to define validation rules for the above class, so we have to create a new validator class like 'PersonViewModelValidator.cs' in a 'Validators' folder like below.
Validators/PersonViewModelValidator.cs:
using FluentValidation;
using FluentValidationDemo.MVC.Models;

namespace FluentValidationDemo.MVC.Validators
{
    public class PersonViewModelValidator:AbstractValidator<PersonViewModel>
    {
        public PersonViewModelValidator()
        {
            RuleFor(_ => _.FirstName).NotEmpty().Length(4,12);
            RuleFor(_ => _.Age).GreaterThan(10);
        }
    }
}
  • (Line: 6) To create a validator class it should inherit 'FluentValidation.AbstractValidator<TModel>' where 'TModel' is the type of our model that we want to enable the validation rules
  • All validation rules have to be defined inside of our validator class constructor.
  • (Line: 10)  Here I applied two validation rules for the 'FirstName' property like 'NotEmpty'(that means field can't be the empty string) and 'Length(4,12)' defined string range with min and max values.
  • (Line: 11) Here I applied only one validation rule like 'Age' property needs to be greater than some specified limit value.
Let's create an MVC view where we can observe server-side validations firing as per our validation rules. So let's create a new controller like 'PersonController.cs'.
Controllers/PersonController.cs:
using FluentValidationDemo.MVC.Models;
using Microsoft.AspNetCore.Mvc;

namespace FluentValidationDemo.MVC.Controllers
{
    [Route("person")]
    public class PersonController : Controller
    {
        
        [HttpGet]
        [Route("create")]
        public IActionResult Create()
        {
            return View();
        }

        [HttpPost]
        [Route("create")]
        public IActionResult Create(PersonViewModel person)
        {
            if (ModelState.IsValid)
            {
                return Content("Success");
            }
            return View(person);
        }
    }
}
  • (Line: 10-15) Defined a HttpGet action method, its just displays our page.
  • (Line: 17-26) Define a HttpPost action method. At #Line21 checking our model is valid or not
Views/Person/Create.cshtml:
@model FluentValidationDemo.MVC.Models.PersonViewModel

<div>
    <form asp-action="create" method="post">
        <div class="form-group row">
            <label asp-for="FirstName" class="col-sm-2 col-form-label">Name</label>
            <div class="col-sm-10">
                <input asp-for="FirstName" type="text" class="form-control" />
                <span asp-validation-for="FirstName" class="text-danger"></span>
            </div>
        </div>
        <div class="form-group row">
            <label asp-for="Age" class="col-sm-2 col-form-label">Name</label>
            <div class="col-sm-10">
                <input asp-for="Age" type="text" class="form-control" />
                <span asp-validation-for="Age" class="text-danger"></span>
            </div>
        </div>
        <div class="form-group row">
            <button type="submit" class="btn btn-primary">Submit</button>
        </div>
    </form>
</div>
  • (Line: 1) Defined model for our razor view.
  • Created a small form with MVC model binding using razor syntax.
Now open the page and enter some invalid data into the form and click on submit button error messages will be displayed as below.

Implement Fluent Validation For Nested Model:

Now let's explore how fluent validation rules are applied for the nested model. Let's create a child view model like 'PersonAddressViewModel.cs'.
Models/PersonViewModel.cs & Models/PersonAddressViewModel.cs:
namespace FluentValidationDemo.MVC.Models
{
    public class PersonViewModel
    {
        public int ID { get; set; }
        public string LastName { get; set; }
        public string FirstName { get; set; }
        public int Age { get; set; }
		
		// child navigation property
        public PersonAddressViewModel PersonAddress { get; set; }
    }
}


namespace FluentValidationDemo.MVC.Models
{
    public class PersonAddressViewModel
    {
        public int PersonAddressId { get; set; }
        public string AddressLine1 { get; set; }
        public string AddressLine2 { get; set; }
        public string City { get; set; }
        public string State { get; set; }
        public string Country { get; set; }
    }
}
  • (Line: 11) Child class(PersonalAddressViewModel) navigation property.
  • (Line: 18-26) Add new child class like 'PersonAddressViewModel'.
Now let's create a validator class for 'PersonAddressViewModel' like 'PersonAddressViewModelValidator.cs' where we have to apply the validation rules.
Validators/PersonAddressViewModelValidators.cs:
using FluentValidation;
using FluentValidationDemo.MVC.Models;

namespace FluentValidationDemo.MVC.Validators
{
    public class PersonAddressViewModelValidator: AbstractValidator<PersonAddressViewModel>
    {
        public PersonAddressViewModelValidator()
        {
            RuleFor(_ => _.AddressLine1).NotEmpty();
        }
    }
}
  • (Line: 6) Inherited 'FluentValidation.AbstractValidotr<TModel>'.
  • (Line: 10) For the 'AddressLine1' property applied a validation rule like it can't be empty.
let's update our view(Create.cshtml) with an additional textbox that to bind our child class property like 'AddressLine1'.
Views/Person/Create.cshtml:
@model FluentValidationDemo.MVC.Models.PersonViewModel


<div>
    <form asp-action="create" method="post">
        <div class="form-group row">
            <label asp-for="FirstName" class="col-sm-2 col-form-label">Name</label>
            <div class="col-sm-10">
                <input asp-for="FirstName" type="text" class="form-control" />
                <span asp-validation-for="FirstName" class="text-danger"></span>
            </div>
        </div>
        <div class="form-group row">
            <label asp-for="Age" class="col-sm-2 col-form-label">Age</label>
            <div class="col-sm-10">
                <input asp-for="Age" type="text" class="form-control" />
                <span asp-validation-for="Age" class="text-danger"></span>
            </div>
        </div>
        <div class="form-group row">
            <label asp-for="PersonAddress.AddressLine1" class="col-sm-2 col-form-label">Address1</label>
            <div class="col-sm-10">
                <input asp-for="PersonAddress.AddressLine1" type="text" class="form-control" />
                <span asp-validation-for="PersonAddress.AddressLine1" class="text-danger"></span>
            </div>
        </div>

        <div class="form-group row">
            <button type="submit" class="btn btn-primary">Submit</button>
        </div>
    </form>
</div>
  • (Line: 20-26) A new text field added for 'AddressLine1'
By default, fluent validation doesn't fire the validation rules of child class directly. So to enable we have to configure our service with an additional option as below:
Startup.cs:
services.AddControllersWithViews()
.AddFluentValidation(options =>
{
	options.RegisterValidatorsFromAssemblyContaining(typeof(Startup));
	options.ImplicitlyValidateChildProperties = true;
});
  • (Line: 5) The 'ImplicitlyValidateChildProperties' set to 'true' will fire child class properties validation rules automatically.
Now let's go to our page and enter invalid data and check the error messages as below.

CustomizeValidator Attribute:

Fluent Validation provides an attribute called 'CustomizeValidator'. With this attribute, we can only validate the required properties we want, unspecified properties validation won't fire. But it won't have control over the child-class property.

So let's update our post-action method with this CustomizeValidator attribute.
Controllers/PersonController.cs:
[HttpPost]
[Route("create")]
public IActionResult Create([CustomizeValidator(Properties ="Age")] PersonViewModel person)
{
	if (ModelState.IsValid)
	{
		return Content("Success");
	}
	return View(person);
}
  • (Line: 3) Payload decorated with 'FluentValidation.AspNetCore.CustomizedValidator' attribute. To this attribute, we have to pass the properties to which we want to fire the validation rules.

Video Session:

Support Me!
Buy Me A Coffee PayPal Me

Wrapping Up:

Hopefully, I think this article delivered some useful information on the FluentValidation library in the AspNet 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

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'

.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

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

.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

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

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

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

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

ReactJS(v18) Authentication With JWT AccessToken And Refresh Token

In this article, we are going to do ReactJS(v18) application authentication using the JWT Access Token and Refresh Token. JSON Web Token(JWT): JSON Web Token is a digitally signed and secured token for user validation. The JWT is constructed with 3 important parts: Header Payload Signature Create ReactJS Application: Let's create a ReactJS application to accomplish our demo. npx create-react-app name-of-your-app Configure React Bootstrap Library: Let's install the React Bootstrap library npm install react-bootstrap bootstrap Now add the bootstrap CSS reference in 'index.js'. src/index.js: import 'bootstrap/dist/css/bootstrap.min.css' Create A React Component 'Layout': Let's add a React component like 'Layout' in 'components/shared' folders(new folders). src/components/shared/Layout.js: import Navbar from "react-bootstrap/Navbar"; import { Container } from "react-bootstrap"; import Nav from "react-boot

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