Skip to main content

.NET 9 upgrade–notnull constraint

With the Christmas Holidays after us, I finally got some time to start upgrading some older .NET Core applications to .NET 9. First thing I noticed after upgrading is that I got some new warnings related to the ‘notnull’ constraint.

The ‘notnull’ constraint was introduced as part of the nullable reference types feature in C#.  The goal of nullable reference types was to solve the ‘million dollar mistake’ and help you to prevent common issue of null reference exceptions. They allow  to explicitly state whether a reference type variable can be null or not, helping to catch potential null dereferences at compile time.

The feature is in fact a combination of multiple elements all with the goal of avoiding unexpected null reference exceptions:

  • Nullable and Non-Nullable Reference Types:

    • Non-Nullable: If you declare a reference type without the ? suffix (e.g., string name), it is considered non-nullable. The compiler issues warnings if you try to assign a null value to it.

    • Nullable: If you declare a reference type with the ? suffix (e.g., string? name), it can hold a null value. The compiler warns you when you might dereference it without a null check.

  • Null-State Analysis: The compiler tracks the null-state of each variable, which can be either not-null or maybe-null. It issues warnings if there's a possibility of a null dereference.

  • Annotations and Attributes: You can use various attributes (like [NotNullWhen(false)]) and annotations to give the compiler more information about the nullability of parameters and return values in methods.

    • As part of this feature a new generic constraint was introduced, the ‘notnull’ constraint. This guarantees that the provided type is a non-nullable type. This can either be a non-nullable reference type or a non-nullable value type.

    Remark: As this feature was introduced already in C# 8.0, I think it is just a coincidence I noticed it only after upgrading to .NET 9. One extra reason to enable the ‘Treat warnings as errors’ flag…

    I got 2 places where I got this warning:

    ModuleExtensions.cs(83,137,83,144): warning CS8714: The type 'T' cannot be used as type parameter 'TKey' in the generic type or method 'Dictionary<TKey, TValue>'. Nullability of type argument 'T' doesn't match 'notnull' constraint.

    NoOpLogger.cs(15,24,15,34): warning CS8633: Nullability in constraints for type parameter 'TState' of method 'NoOpLogger.BeginScope<TState>(TState)' doesn't match the constraints for type parameter 'TState' of interface method 'ILogger.BeginScope<TState>(TState)'. Consider using an explicit interface implementation instead.

    Here is each time the original code and the fix:

    Original code:

    Fix:

    Original code:

    Fix:

    More information

    Nullable reference types - C# | Microsoft Learn

    The history of C# | Microsoft Learn

    Labels:

    Popular posts from this blog

    .NET 8–Keyed/Named Services

    A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
    Read more

    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