Skip to main content

Using legacy text encodings in .NET Core

Upgrading an (old) .NET application to .NET core turned into a learning experience when we got the following error message after the upgrade was done:

System.NotSupportedException : No data is available for encoding 1252. For information on defining a custom encoding, see the documentation for the Encoding.RegisterProvider method.

TLDR; The application was using an older Windows-1252 text encoding causing the error above when trying to use this in .NET Core which doesn’t support this encoding out-of-the-box.

Introduction to Text Encodings

Text encoding is a method used to convert text data into a format that can be easily processed by computers. Computers inherently understand numbers, not characters, so text encoding maps characters to numerical values. This process ensures that text data can be stored, transmitted, and interpreted correctly across different systems and platforms.

There are various text encodings, each designed to support different sets of characters. Some common encodings include:

  • ASCII: Supports basic English characters.

  • UTF-8: A versatile encoding that supports a wide range of characters from different languages.

  • ISO-8859-1: Also known as Latin-1, supports Western European languages.

  • Windows-1252: A superset of ISO-8859-1, commonly used in Windows environments.

The error: System.NotSupportedException: No data is available for encoding 1252

When working with .NET Core, you might encounter the error message: System.NotSupportedException: No data is available for encoding 1252. This error occurs because .NET Core does not include support for certain legacy encodings, such as Windows-1252, by default.

How to fix the error in .NET Core

To resolve this issue, you need to register the CodePagesEncodingProvider from the System.Text.Encoding.CodePages package. This package provides support for various code pages, including Windows-1252.

Here are the steps to fix the error:

  • Install the System.Text.Encoding.CodePages Package: Open your project in Visual Studio or your preferred IDE and run the following command in the Package Manager Console:     

    dotnet add package System.Text.Encoding.CodePages
    

  • Register the CodePagesEncodingProvider: In your application's startup code, register the CodePagesEncodingProvider to enable support for the required encoding. Add the following code:

  • Use the Encoding: Now, you can use the Windows-1252 encoding in your application without encountering the System.NotSupportedException error. For example:

By following these steps, you can ensure that your .NET Core application supports the Windows-1252 encoding and avoid the System.NotSupportedException error.

 

More information

How to use character encoding classes in .NET - .NET | Microsoft Learn

CodePagesEncodingProvider Class (System.Text) | Microsoft Learn

NuGet Gallery | System.Text.Encoding.CodePages 9.0.2

https://www.nuget.org/packages/System.Text.Encoding.CodePages/

Popular posts from this blog

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

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.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...