Skip to main content

warning SYSLIB1037: The type '' defines init-only properties, deserialization of which is currently not supported in source generation mode.

2 days ago I introduced the System.Text.Json source generator and showed you how to use it in ASP.NET Core. What I didn’t told you that it didn’t go so smoothly.

If you had a good look at the generated code I shared, you maybe noticed the following lines:

The generated setter on the property will not work and instead throw an InvalidOperationException.

This also appears as a warning during the build process:

CSC : warning SYSLIB1037: The type 'OrderDto' defines init-only properties, deserialization of which is currently not supported in source generation mode.

More information about this warning: https://docs.microsoft.com/en-us/dotnet/fundamentals/syslib-diagnostics/syslib1037

The reason is that my OrderDto is a record type using init-only properties:

There is not much we can do to fix this else then switching to mutable properties:

I searched around further on the web about this issue and found the following related Github issues:

The good news that Microsoft is looking into this issue and that maybe a solution will be provided in .NET 7.

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