Skip to main content

ImageSharp–Image.Load() Compiler error after updating

On one of my pet projects I’m using ImageSharp to manipulate images. It is a great library that comes with a lot of features in it. And performance and memory usage is good which is quite important when manipulating images. 

Remark: Be aware that a commercial license is needed in some conditions. So check out the pricing page before adding this library to your application.

I decided to add some new stuff but before I did that I updated the library to the latest version. However after doing that my original code no longer compiled. Let’s see how we can fix this…

Here is the original code:

This specific overload no longer exists in the latest version. So I started to update my code to a supported overload:

Remark: Notice that I also switched to an async overload but know that a synchronous version exists as well.

However by doing that I no longer had the format information available. The good news is that this information could now be accessed through the image.Metadata property:

The compiler was happy again and I as well as I  could continue coding.

More information

SixLabors/ImageSharp: :camera: A modern, cross-platform, 2D Graphics library for .NET (github.com)

Six Labors : ImageSharp

Labels:

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

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

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