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

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.

The art of simplicity

Search This Blog