Skip to main content

Visual Studio 2022 17.12- Show inline return values while debugging

With the 17.12 version of Visual Studio 2022 there comes a feature that I was waiting to be added for a long time(and with long I really mean long). Of course you are wondering what feature I'm talking about.

Let me first set the scene by showing you the class I want to debug:

I created a small Calculator example. Notice that I'm using 2 different syntaxes(the regular syntax and expression-bodied method). This is not an accidental inconsistency from my side as you’ll see later.

Now what if I wanted to debug the return values of these functions. Before the latest Visual Studio update I typically used a temporary variable to inspect the return values or took a look at the Autos window or the Watch window.

With this release, you finally see the return statements inline in the editor window.

Here is an example where I added the breakpoint at the end of the function:

Unfortunately this doesn’t work (yet?) when using the expression-bodied method syntax, this is because the breakpoint is set on the method body before it is executed:

Still this remains a top feature!

More information

Tips and tricks in the debugger - Visual Studio (Windows) | Microsoft Learn

Expression-bodied members - C# | 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.

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

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...