Skip to main content

NDepend–DDD Rule

A few weeks ago I was contacted by Patrick Smacchia, the creator of NDepend, if I would check out the latest edition of their code quality tool. As I had an upcoming software audit assignment planned, I thought it would be a great occasion to see what NDepend brings to the table and how it can help me to improve my understanding of an unfamiliar codebase.

NDepend offers a lot of rules that are evaluated against your code. These rules can help you identify all kind of issues in your code.

If you want to learn more about this feature check out the following video:

 

All these rules are created using CQLinq(the code query language of NDepend) and can be customized to your needs (and the specificalities of your project).

One rule that got my interest was the ‘DDD -  ubiquitous language check’. This rule allows you to check if the correct domain language terms are used. It is disabled by default(because it should be updated to reflect your domain language).

Let’s see how to update this rule and enable it:

  • Open up the Queries and Rules explorer in Visual NDepend:
  • Browse to the Naming Conventions section:
  • On the right you’ll find the DDD rule in the list of rules

  • Check the checkbox to enable the rule

  • Click on the rule to open the edit window. Here you can update the CQLinq query to make it correspond with the ubiquitous language of your domain

  • After changing the rule, click on the ‘Save’ icon to start using the updated rules
Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more