Skip to main content

Error CS0534: '' does not implement inherited abstract member 'JsonSerializerContext.GeneratedSerializerOptions.get'

After introducing the System.Text.Json source generator in one of my projects, I happily moved on to another task. Until I got a build failed message from the CI build.

A look at the build logs showed the following error messages:

##[error]Example.Services\Infrastructure\JsonContext.cs(13,28): Error CS0534: 'JsonContext' does not implement inherited abstract member 'JsonSerializerContext.GeneratedSerializerOptions.get'

D:\b\3\_work\90\s\Example.Services\Infrastructure\JsonContext.cs(13,28): error CS0534: 'JsonContext' does not implement inherited abstract member 'JsonSerializerContext.GeneratedSerializerOptions.get' [D:\b\3\_work\90\s\Example.Services\Example.Services.csproj]

##[error]Example.Services\Infrastructure\JsonContext.cs(13,28): Error CS0534: 'JsonContext' does not implement inherited abstract member 'JsonSerializerContext.GetTypeInfo(Type)'

D:\b\3\_work\90\s\Example.Services\Infrastructure\JsonContext.cs(13,28): error CS0534: 'JsonContext' does not implement inherited abstract member 'JsonSerializerContext.GetTypeInfo(Type)' [D:\b\3\_work\90\s\Example.Services\Example.Services.csproj]

Strange! The local build succeeded without any issue. What could be wrong?

I scrolled further through the log file and noticed the following warning:

C:\Program Files\dotnet\sdk\6.0.106\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.DefaultItems.targets(134,5): warning NETSDK1182: Targeting .NET 6.0 in Visual Studio 2019 is not supported. [D:\b\3\_work\90\s\VLM.IAM.Services.Tests\VLM.IAM.Services.Tests.csproj]

##[warning]C:\Program Files\dotnet\sdk\6.0.106\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.DefaultItems.targets(134,5): Warning NETSDK1182: Targeting .NET 6.0 in Visual Studio 2019 is not supported.

I did upgrade the project to .NET 6 before I introduced the source generator. Could the error above be related to this warning?

In the build pipeline I was still using the Visual Studio Build task to build my project. This task does not support yet Visual Studio 2022 when using Azure DevOps Server. We’ll have to wait for the Azure DevOps Server 2022 release before we can build a .NET 6 project with this task.

So to build a .NET 6 project, we’ll have to switch to the .NET Core CLI task.

This time when I triggered the CI build, both the warning and the 2 errors are gone.

Labels:

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

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

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