.NET

In the realm of software development, ensuring the quality of the data you're handling is paramount. With the rise of Microservices, CQRS (Command Query Responsibility Segregation) and Mediator patterns, developers now, more than ever, need a reliable mechanism to validate data before processing it. Enter Command Handler Validators - a mechanism to validate command objects before they're handled. In this blog post, we'll discuss how to implement a Command Handler Validator using MediatR, FluentValidation, and ASP.NET Core. A Practical Example Consider the following code for creating a new customer: public class CreateCustomerCommand : IRequest { public string FirstName { get; set; } public string LastName { get; set; } public string Email { get; set; } } The CreateCustomerCommand command is then handled by CreateCustomerCommandHandler: public class CreateCustomerCommandHandler : IRequestHandler { public async Task Handle(CreateCustomerCo...

Introduction The Decorator Pattern is a structural design pattern that allows you to dynamically add new functionality to an object without changing its existing behaviour. This pattern is highly effective in situations where you need to extend the functionality of an object without making changes to its code or using inheritance. In this blog post, we will discuss the decorator pattern in .NET using a real-world example. Consider a scenario where you have a list of players and you need to fetch the list from a service. The service might take a considerable amount of time to return the list of players. You may want to add caching or logging functionality to the service, but you don't want to modify the existing code. This is where the decorator pattern comes into play. Example Define the Interface First, we define the interface IPlayersService with a single method, GetPlayersList(): public interface IPlayersService { IEnumerable GetPlayersList(); } Implement the Interface ...

Introduction Unit testing is an essential practice in modern software development. It helps ensure that individual components of a system work as expected and promotes robust, maintainable code. In this blog post, we will explore how to supercharge your unit testing by combining three powerful tools: MOQ, Dependency Injection, and Fluent Assertions. We will learn how to create flexible, easy-to-read tests that will make your code more resilient and your development process more enjoyable. The Importance of Unit Testing Unit testing refers to the process of testing individual units or components of an application in isolation. This practice helps identify and fix issues early in the development process, making it easier to maintain and extend the codebase. In addition to improving code quality, unit tests serve as documentation, providing valuable insight into the expected behavior of a system. Getting Started with MOQ MOQ is a popular .NET library for creating mock objects, which are s...