Skip to main content

C#–Declaring attributes on positional record types

In C# 9 record types were introduced.

A record in C# is a class or struct that provides special syntax and behavior for working with data models.

What makes them different from a ‘normal’ class or struct is that they offer the following functionality:

  • Value equality: Two record types are equal if the types match and all property and fields match
  • Immutability: You cannot change any property or field value after instantiation

You have 2 ways to define a record type. One way is similar to what you already know when creating classes or structs:

A second way is through positional parameters:

Behind the scenes, the compiler does a lot of work for us as it creates:

  • A public autoimplemented property for each positional parameter provided in the record declaration
  • A primary constructor whose parameters match the positional parameters on the record declaration.  
  • A Deconstruct method with an out parameter for each positional parameter provided in the record declaration. The method deconstructs properties defined by using positional syntax; it ignores properties that are defined by using standard property syntax.

This makes our live a lot easier. No reason to complain.

But what if we want to add metadata to the generated properties?

Good question! The good news is that we can declare attributes at the positional parameter level and specify a target:

 

In the example above the System.Text.Json.Serialization.JsonPropertyNameAttribute is assigned to each property of the Person record. The property target is used to specify that the attribute applies to the compiler-generated property.

More information

Records in C# - C# | Microsoft Learn

Records - C# reference - C# | Microsoft Learn

Popular posts from this blog

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

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.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...