Skip to main content

Impress your colleagues with your knowledge about..the PrintMembers method

Sometimes when working with C# you discover some hidden gems. Some of them very useful, other ones a little bit harder to find a good way to benefit from their functionality. One of those hidden gems that I discovered some days ago is the PrintMembers method.

Record Types

To explain where you can find this method, I first have to talk about record types.  Record types were introduced in C# 9 as a new reference type that you can create instead of classes or structs. C# 10 adds record structs so that you can define records as value types.

Records are distinct from classes in that record types use value-based equality. Two variables of a record type are equal if the record type definitions are identical, and if for every field, the values in both records are equal.

Record types have a compiler-generated ToString method that displays the names and values of public properties and fields:

Person{ FirstName = Bart, LastName = Wullems }

In an application we are building we are using this ToString() method to generate a cache key. This works great until you add another reference type to your record type:

If we now print out the value, we see the following:

Product { FirstName = Bart, LastName = Wullems, PhoneNumbers = System.String[] }

We no longer have uniqueness what doesn’t make it a good cache key anymore.

PrintMembers

Let’s fix this by implementing a PrintMembers method on our record type.

Important! If you want to do this,  you need to be aware about the following:

  • For a sealed record that derives from object (doesn't declare a base record): private bool PrintMembers(StringBuilder builder);
  • For a sealed record that derives from another record (note that the enclosing type is sealed, so the method is effectively sealed): protected override bool PrintMembers(StringBuilder builder);
  • For a record that isn't sealed and derives from object: protected virtual bool PrintMembers(StringBuilder builder);
  • For a record that isn't sealed and derives from another record: protected override bool PrintMembers(StringBuilder builder);

Here is the implementation for our Person class:

If we now print out the value,  all the values are included:

Product { FirstName = Bart, LastName = Wullems, PhoneNumbers = 123/45.67.89,987/65.43.21 }

Nice!

More information:

Records - C# reference | 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’: ...