Skip to main content

Type Aliases in C#: Bringing F#-style readability to your C# code

As I like to to program not only in C# but also F#, there are some paradigms and features in F# that influence my C# coding style. One of those features is F# type abbreviations that make complex type signatures more understandable and expressive. Since C#12, you have a similar feature available in C#: type aliases using the using directive.

But although this option already exists for some time, I don’t see many C# developers use it. But I’ll hope that this blog post can help to change this and increase adoption…

What are Type Aliases?

Type aliases allow you to create shorthand names for existing types, making your code more readable and self-documenting. Instead of repeatedly writing complex generic types or lengthy class names, you can define a meaningful alias that captures the intent of your data structure.

The F# connection

In F#, type abbreviations have been a feature for years:

These abbreviations don't create new types—they're simply aliases that make the code more expressive and easier to understand.

C# Type Aliases in action

C# 12 brings this capability to C# developers through enhanced using statements at the file level:

For me type aliases really shine in domain-driven design where you want to avoid primitive obsession and be more explicit:

Benefits and limitations

The benefits of using (no pun intended) this feature are obvious:

  • Improved readability: Code becomes self-documenting
  • Reduced cognitive load: Less mental parsing of complex type signatures
  • Better refactoring: Change the underlying type in one place
  • Domain clarity: Express business concepts more clearly in code

Unfortunately compared to F# type abbreviations, C# type aliases still have some limitations:

  • File scope only: Aliases are limited to the file where they're declared
  • No type safety: Aliases don't create distinct types—they're purely cosmetic
  • No IntelliSense benefits: The underlying type still appears in tooltips and errors

While they don't provide the same level of type safety as distinct types, they offer a lightweight way to make your code more readable and self-documenting.

More information

Alias any type - C# feature specifications | Microsoft Learn

Type Abbreviations - F# | Microsoft Learn

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.

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...

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         ...