Code on Dimitri Laaraybi

Exploring Extension Members in C# 14

Wed, 24 Dec 2025 00:00:00 +0000

C# 14 introduces one of the most requested language features in years: Extension Members.
While C# has long supported extension methods, the new extension member system dramatically expands what developers can add to types they don’t control, enabling us to do pretty much whatever we want with non-user types 🔥
In this article, we’ll try to explain what are those new extension members and how to use it properly, so let’s go !

Reducing dependencies with the IServiceUtils pattern

Sat, 26 Jul 2025 00:00:00 +0000

Introduction

In many C#/.NET applications, business services rely on common dependencies like logging, mapping, time management, or database repositories.
Injecting these repeatedly into every service can lead to boilerplate code, inconsistency and less room for dependancies with relevant business logic value.
Another drawback of this is that potential code scanners like Sonar could eventually raise some rules errors when some of your constructors injects too much parameters (which is the case by default in Sonar C# rules, 7 max allowed 😉). And this rule break could potentially block your quality gate ❌

Beware of Task.Run() !

Tue, 18 Mar 2025 00:00:00 +0000

Introduction

Hey all ! 🫡

A little post to share some thoughts about the Task.Run() method, and the problems you could encounter especially in a .NET API using a GlobalExceptionHandler. ❌

What actually happen when you need to start a Task as “fire and forget”, and you have an ExceptionHandler configured globally ?

This kind of case can happen frequently, for example if you need to await a particular business process, and start some tasks after that process that does not need to be awaited by the calling context.

No, FluentAssertions is not the only one... Here is how to switch from FluentAssertions to Shouldly !

Sun, 02 Mar 2025 00:00:00 +0000

Introduction

Hey all ! 🫡

Let’s talk about another little drama that has been shaking the .NET community during the last weeks.
When working on unit tests in .NET, developers often rely on assertion libraries to make their tests more readable and expressive.
Two popular libraries in this space are FluentAssertions and Shouldly. While both libraries serve the same purpose, one of them actually updated its licensing model and frightened the whole community about his new goal, making money 😂 (Well who does not want to)
And this one is FluentAssertions.
In fact, it now requires a paid licence to be used for commercial use. At least, concerning the 8.x.x version. The developers have stated that the 7.x.x version will be forever free and receive critical fixes, but this strange move from their side may have pushed you to find another library for your assertions, to avoid any problems with the company you work for.
If that’s the case, here is a little tutorial that explains how to migrate from FluentAssertions to Shouldly !

How to switch from Moq to NSubstitute after the SponsorLink scandal ?

Thu, 17 Aug 2023 00:00:00 +0000

Hey devs ! 😁

If you are a .NET developer who uses the popular mocking library Moq for your unit tests, you may have heard about the recent controversy that erupted when it was revealed that Moq was secretly collecting and sending user email addresses to a third-party service called SponsorLink. This was done without the consent or knowledge of the developers who used Moq , and raised serious privacy and security concerns.
In this post, I’ll try to explain in more details what this scandal is all about and how to switch from Moq to NSubstitute if you see fit, but also how to prevent your projects from those vulnerabilities in a DevSecOps way 😉