Skip to main content

.NET 8– Upgrade warnings

As our policy is to keep our .NET applications on the latest LTS version, we started to upgrade our application portfolio to .NET 8. Changing the Target Framework Moniker and updating the ASP.NET Core NuGet packages was sufficient to get the upgrade done.  However the upgrade also triggered some warnings and because we had ‘Treat warnings as errors’ enabled in Visual Studio, our applications refused to compile.

SYSLIB0051

The first warning we got was SYSLIB0051:

Severity

Code

Description

Project

File

Line

Suppression State

Warning

SYSLIB0051

'Exception.Exception(SerializationInfo, StreamingContext)' is obsolete: 'This API supports obsolete formatter-based serialization. It should not be called or extended by application code.'

SOFACore

C:\source\repos\SOFACore\Configuration\ConfigurationException.cs

20

Active

For every exception class we had a specific constructor that was only used for serialization purposes. As this constructor was intended to support remoting and remoting is not supported in .NET Core it doesn’t make sense to keep this constructor.

We got rid of this warning by removing all the serialization constructors for our Exception classes.

SYSLIB0049

A second (less frequent) warning we got SYSLIB0049:

Severity

Code

Description

Project

File

Line

Suppression State

Warning

SYSLIB0049

'JsonSerializerOptions.AddContext<TContext>()' is obsolete: 'JsonSerializerOptions.AddContext is obsolete. To register a JsonSerializerContext, use either the TypeInfoResolver or TypeInfoResolverChain properties.'

eShopExample

C:\source\repos\SOFACore\Example\eShopExample\Startup.cs

55

Active

In our code we use a custom JsonContext to configure how serialization should be handled by System.Text.Json:

The JsonSerializerOptions.AddContext<TContext>() method was introduced in .NET 6 as a means to associate JsonSerializerOptions instances with a specified JsonSerializerContext type. This method was superseded in .NET 7 with the introduction of contract customization and the TypeInfoResolver property.

As the JsonSerializerContext type implements the ITypeInfoResolver interface , we can easily get rid of this warn by updating our code like this:

In the code above the JsonContext class is our own implemented JsonSerializerContext:

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

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

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