Skip to main content

Nullable reference types–Using the required keyword in C# 11

A few years ago with the introduction of Nullable Reference Types in C# 8, I blogged about a way to get rid of the CS8618 compiler warning for your DTO’s and ViewModels. The trick I shared was to use a a property assignment with a default literal:

Although this  solution works it defeats the point of nullable reference types, as the idea is it would help you to get rid of unexpected NullReferenceExceptions. Instead the only thing you got is a compiler that no longer complaints.

With the release of C# 11, a better solution exists through the usage of the required modifier.

The required modifier indicates that the field or property it's applied to must be initialized by all constructors or by using an object initializer.

Let’s update our code:

Now the compiler expects that the property is always set, so the compiler warning disappears.

Remark: The required modifier is enforced at compile time. So it is still possible that we end up with a NullReferenceException when for example the object is created through deserialization of a JSON document.

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

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
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