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

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

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.

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