System.Drawing.Common is not supported on non-Windows platforms

[qcjxberin]

System.PlatformNotSupportedException: System.Drawing.Common is not supported on non-Windows platforms. See https://aka.ms/systemdrawingnonwindows for more information.
at System.Drawing.LibraryResolver.EnsureRegistered() in System.Drawing.Common.dll:token 0x600058c+0x11
at System.Drawing.SafeNativeMethods.Gdip.PlatformInitialize() in System.Drawing.Common.dll:token 0x6000b00+0x0
at System.Drawing.SafeNativeMethods.Gdip..cctor() in System.Drawing.Common.dll:token 0x6000af8+0x2b

https://aka.ms/systemdrawingnonwindows can't be open,How to solve this problem

[svick]

The exception message is correct: System.Drawing.Common is no longer supported on .Net 6 on Linux and macOS. For more information, see this document and dotnet/docs#25257.

As that document states, if you want to continue using it on .Net 6, you can provide a runtime config switch named System.Drawing.EnableUnixSupport set to true. But even this will not work starting with .Net 7.

As for the aka.ms link, I'm not sure. Maybe it will be set up once this breaking change is properly documented (i.e. when dotnet/docs#25367 is merged).

[mairaw]

It seems @svick has answered your question, so I’m closing this issue. Let me know if I missed anything.

[mairaw]

Reopening since the link goes to our internal tool somehow.
Tagging @ericstj @danmoseley @terrajobst @safern who seem to own that link.

[safern]

Tagging @ericstj @danmoseley @terrajobst @safern who seem to own that link.

I'll work with @gewarren to post the doc ASAP on Monday and point the url to the doc.

[gewarren]

@safern Here is the PR; it's ready for review: dotnet/docs#25367

[safern]

https://aka.ms/systemdrawingnonwindows should now resolve to the published docs. Thanks for the report.

[janseris]

What is the solution for this for developers?
I have a web server application running on Linux and I need to know what replaces System.Drawing for .NET 6 and later. I read in the documentation that

recommended alternatives include ImageSharp, SkiaSharp, Windows Imaging Components, and Microsoft.Maui.Graphics.

So now developers will use multiple libraries and .NET will have no standard image manipulation API at all?
Which one of these is the right one? For which one Microsoft can guarantee support for the next years? What are we supposed to do when these random package authors change license or drop support?
So now when people will want to learn .NET image manipulation, there will be package-specific tutorials?
MAUI image API support might not be dropped but instead, it is a UI library so depending on MAUI on an ASP.NET server application which does not relate to MAUI in any way is ridiculous.
What is the 1 and only suggested solution which will be supported by Microsoft just as .NET 6 is (LTS) etc.?

What is the suggested solution for Blazor WebAssembly projects needing to resize image before uploading to server? MAUI graphics API?

Thanks

[danmoseley]

@mattleibow can you confirm that SkiaSharp is fully supported by Microsoft?

Also, I have generally thought of SkiaSharp as client focused, and something like ImageSharp better for servers. Is it reasonable to use SkiaSharp on the server side? I know that unlike ImageSharp, it has some native dependencies.

[siddjain]

I am using System.Drawing.Common on Mac OS but with target framework 6.0 and have set

{
  "runtimeOptions": {
    "tfm": "net6.0",
    "framework": {
      "name": "Microsoft.NETCore.App",
      "version": "6.0.0"
    },
"configProperties": {
      "System.Drawing.EnableUnixSupport": true
   }
  }
}

but still seeing this exception:

Unhandled exception. System.PlatformNotSupportedException: System.Drawing.Common is not supported on this platform.
   at System.Drawing.SystemFonts.get_DefaultFont()

can anyone help please?

[gewarren]

@siddjain Which file are those settings from?

[siddjain]

the settings are from myapplication.runtimeconfig.json under bin/Debug/net6.0-windows of the project root. I am trying to run the application from the project root using dotnet run. Thanks for your help.

[gewarren]

What does your project file look like? I'm surprised the output folder is net6.0-windows on macOS.

[siddjain]

its because I have set it so. setting it to net6.0-macos gave me another set of issues. here is the csproj file:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net6.0-windows</TargetFramework>
    <Nullable>enable</Nullable>
    <ImplicitUsings>enable</ImplicitUsings>
    <RootNamespace>MyApp</RootNamespace>
    <AssemblyName>MyApp</AssemblyName>    
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="CommandLineParser" Version="2.9.1" />
    <PackageReference Include="System.Drawing.Common" Version="7.0.0" />
  </ItemGroup>
</Project>

[gewarren]

Looks like you're using the 7.0 version of System.Drawing.Common. Does it work if you set that to 6.0.0?

[siddjain]

no it still doesn't work

Unhandled exception. System.TypeInitializationException: The type initializer for 'Gdip' threw an exception.
 ---> System.PlatformNotSupportedException: System.Drawing.Common is not supported on non-Windows platforms. See https://aka.ms/systemdrawingnonwindows for more information.
   at System.Drawing.LibraryResolver.EnsureRegistered()
   at System.Drawing.SafeNativeMethods.Gdip.PlatformInitialize()
   at System.Drawing.SafeNativeMethods.Gdip..cctor()
   --- End of inner exception stack trace ---
   at System.Drawing.SafeNativeMethods.Gdip.GdipGetGenericFontFamilySansSerif(IntPtr& fontfamily)
   at System.Drawing.FontFamily.GetGdipGenericSansSerif()
   at System.Drawing.FontFamily.get_GenericSansSerif()
   at System.Drawing.Font.CreateFont(String familyName, Single emSize, FontStyle style, GraphicsUnit unit, Byte charSet, Boolean isVertical)
   at System.Drawing.Font..ctor(String familyName, Single emSize, FontStyle style, GraphicsUnit unit, Byte gdiCharSet, Boolean gdiVerticalFont)
   at System.Drawing.Font..ctor(String familyName, Single emSize, String systemName)
   at System.Drawing.SystemFonts.get_DefaultFont()

[siddjain]

made some changes and that error is fixed but I get a new one now:

Unhandled exception. System.TypeInitializationException: The type initializer for 'Gdip' threw an exception.
 ---> System.DllNotFoundException: Unable to load shared library 'libgdiplus' or one of its dependencies. In order to help diagnose loading problems, consider setting the DYLD_PRINT_LIBRARIES environment variable: dlopen(liblibgdiplus, 0x0001): tried: 'liblibgdiplus' (no such file), '/System/Volumes/Preboot/Cryptexes/OSliblibgdiplus' (no such file), '/usr/lib/liblibgdiplus' (no such file, not in dyld cache), 'liblibgdiplus' (no such file), '/usr/local/lib/liblibgdiplus' (no such file), '/usr/lib/liblibgdiplus' (no such file, not in dyld cache)
   at System.Drawing.SafeNativeMethods.Gdip.GdiplusStartup(IntPtr& token, StartupInput& input, StartupOutput& output)
   at System.Drawing.SafeNativeMethods.Gdip..cctor()

how do I fix this one?

[safern]

@siddjain for that specific error you need to make sure that libgdiplus is installed in your OS.

https://www.mono-project.com/docs/gui/libgdiplus/

In Unix systems you can do it by running sudo apt-get install libgdiplus or whatever is the package manager for that OS.

on mac systems you need to run brew install mono-libgddiplus

Note that using 6.0.0 means that you'd be out of support so the recommended guidelines from the .NET team is to move out of depending on System.Drawing.Common for non windows.

[danmoseley]

@mattleibow just checking you saw my question above as it would be good to know the answer.

[danmoseley]

@siddjain do you have to use System.Drawing? As mentioned, it is out of support now.

[siddjain]

Thanks all for the help. re: do you have to use System.Drawing? to answer literally, its a loaded question. One can always port the code to another library. In fact, I already did it for one of my GDI+ apps as I wanted to learn Swift but to my surprise the C# code runs much faster than Swift!

Also what I understand when someone says the library is out of support is that no one is fixing bugs and issues but anyone is welcome to use it as-is and it will continue to be available and downloadable from the internet. is that correct?

[danmoseley]

Also what I understand when someone says the library is out of support is that no one is fixing bugs and issues but anyone is welcome to use it as-is and it will continue to be available and downloadable from the internet. is that correct?

System.Drawing is not going anywhere, but the code inside it that uses libgdiplus has been removed, which means that it will only work on Windows now.

• in .NET 6, you can enable mac/Linux support, but it is off by default. see See https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/6.0/system-drawing-common-windows-only
• in .NET 7 and later, it does not exist.

.NET 6 will go out of support in due course, although you'll still be able to download it if you don't mind being out of support.

In short, I recommend you don't write code against System.Drawing unless it's only intended to run on Windows. The only exception might be if it's just a temporary thing, in which case you can use .NET 6. But generally you should pick another library to do this stuff unless you're Windows only.

[siddjain]

Thanks Dan for the clarification!

[janseris]

@siddjain

one can always port the code to another library

This part is not magically for free you know especially with large codebase with little automatic tests

[siddjain]

Correct that’s is why it’s a loaded question.

…

Sent from my iPhone On Jan 4, 2023, at 11:48 AM, janseris ***@***.***> wrote:  @siddjain<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgh.neting.cc%2Fsiddjain&data=05%7C01%7C%7Cbf900490cff64091c4c608daee8cb75e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638084585393937304%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=crtyb493yiBDO7zBD8O6aIV5%2Fw9BqF80I%2BqONXduMTI%3D&reserved=0> one can always port the code to another library This part is not magically for free you know — Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgh.neting.cc%2Fdotnet%2Fruntime%2Fissues%2F80148%23issuecomment-1371349313&data=05%7C01%7C%7Cbf900490cff64091c4c608daee8cb75e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638084585393937304%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Uk%2F%2BUWWUd9rpT43AjzQ9cjyRUBB1ETPC7YDqzWhIuME%3D&reserved=0>, or unsubscribe<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgh.neting.cc%2Fnotifications%2Funsubscribe-auth%2FAAFZEMPPAE2U6UOYWCS6KT3WQXH2PANCNFSM6AAAAAATQDMMYA&data=05%7C01%7C%7Cbf900490cff64091c4c608daee8cb75e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638084585393937304%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J8yQTczUNdGk40qqOIZtDm3rwv3S57D3UGnUjYijGWs%3D&reserved=0>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[Rombersoft]

Reading it all I came to the conclusion that I learned not the right programming language. It was necessary to learn Java 10 years ago when C# finished with such valuable problems. Microsoft is a great company but it is not able to make support graphics basics for three OS. I will keep silent about cross-platformed desktop GUI, they are missing. Miguel De Icaza come back. If you advise migrating to MAUI or Skia, maybe will you write a wrapper for it inside Linux System.Drawing implementation?