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.

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

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.