System.Drawing.Common load error after upgrading WPF app to .NET 10 (Publish only)

[aiqinxuancai]

Description

My WPF application (https://github.com/aiqinxuancai/Aria2Fast) has been working flawlessly since its initial upgrade from .NET 6 to .NET 9. Typically, I only need to modify the TargetFramework to complete the upgrade. However, a few days ago when I upgraded it to(VS2026) to .NET 10 and ran it after publishing, it threw the error: "Could not load file or assembly 'System.Drawing.Common, Version=9.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'."

I can reproduce this issue locally. When I downgrade back to .NET 9, the problem resolves immediately.

Strangely, this error doesn't appear during debugging. I'm not sure if the .NET 10 release trimmed the library issues.

Reproduction Steps

First, change the project's TargetFramework to "net10.0-windows". Then, use the following configuration for publishing to reproduce the issue.

<?xml version="1.0" encoding="utf-8"?>
<!--
https://go.microsoft.com/fwlink/?LinkID=208121.
-->
<Project>
  <PropertyGroup>
    <Configuration>Release</Configuration>
    <Platform>Any CPU</Platform>
    <PublishDir>bin\Release\net10.0-windows\publish\win-x64\</PublishDir>
    <PublishProtocol>FileSystem</PublishProtocol>
    <_TargetId>Folder</_TargetId>
    <TargetFramework>net10.0-windows</TargetFramework>
    <RuntimeIdentifier>win-x64</RuntimeIdentifier>
    <SelfContained>true</SelfContained>
    <PublishSingleFile>false</PublishSingleFile>
    <PublishReadyToRun>false</PublishReadyToRun>
  </PropertyGroup>
</Project>

Expected behavior

The executable file runs normally after being published.

Actual behavior

First perform the publish, then run the published exe file, and it prompts an error "Could not load file or assembly 'System.Drawing.Common, Version=9.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'."

Regression?

Can be normally published and run before .Net10

Known Workarounds

Roll back to .Net 9 to publish the exe.

Impact

No response

Configuration

No response

Other information

No response

[lindexi]

@aiqinxuancai Could you add nuget package System.Drawing.Common version 10.0.0 ?

Reference: #11134

Fix by this workaround: #11261 (comment)

[aiqinxuancai]

@aiqinxuancai Could you add nuget package System.Drawing.Common version 10.0.0 ?

I have already found the solution. I need to manually add the NuGet package System.Drawing.Common 10.0.0, and it is also necessary to disable RestoreEnablePackagePruning.
<RestoreEnablePackagePruning>false</RestoreEnablePackagePruning>, only then can the app run normally after publishing. Simply adding the NuGet package System.Drawing.Common is not sufficient.

[nkolev92]

I have already found the solution. I need to manually add the NuGet package System.Drawing.Common 10.0.0, and it is also necessary to disable RestoreEnablePackagePruning.

@aiqinxuancai Does it work if you just disable pruning?

Based on your write-up, I am assuming no, but I'm trying to figure out if it's a pruning thing, or a more general platform thing.

[aiqinxuancai]

I have already found the solution. I need to manually add the NuGet package System.Drawing.Common 10.0.0, and it is also necessary to disable RestoreEnablePackagePruning.

@aiqinxuancai Does it work if you just disable pruning?

Based on your write-up, I am assuming no, but I'm trying to figure out if it's a pruning thing, or a more general platform thing.

My project does not directly reference the Nuget package System.Drawing.Common, it is referenced by other Nuget packages I have introduced. After I directly introduced the System.Drawing.Common version 10.0.0 into Nuget, it displayed this on VS2026:

When I added <RestoreEnablePackagePruning>false</RestoreEnablePackagePruning> to the project, this exclamation mark disappeared.

Additionally, I noticed that if I do not disable RestoreEnablePackagePruning, a NU1510 warning is output during publishing. This issue might be related to these change?
https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/10.0/prune-packagereference-privateassets

1>D:\git\Aria2Fast\Aria2Fast\Aria2Fast.csproj : warning NU1510: PackageReference System.Drawing.Common will not be pruned. Consider removing this package from your dependencies, as it is likely unnecessary.

---

I conducted additional tests, disabling RestoreEnablePackagePruning without explicitly adding the NuGet package System.Drawing.Common, and when I run the exe after publishing, I get this error:

Could not load type 'System.Drawing.IImage' from assembly 'System.Private.Windows.Core, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

(Working fine when debug)

[ericstj]

We had a couple issues WRT to System.Drawing.Common in .NET 10. You will run into two of them, we expect to fix them both in servicing.

Disabling pruning can help with diagnosing the problem but I don't recommend doing so in production. Doing so you end up shipping the package copy of Drawing.Common rather than the framework copy. We'd like folks to use the latest framework copy and not be responsible for updating a package.

dotnet/sdk#51173 (comment) works-around the compilation issue.
dotnet/windowsdesktop#5405 (comment) works-around the load issue for self contained applications.

[aiqinxuancai]

We had a couple issues WRT to System.Drawing.Common in .NET 10. You will run into two of them, we expect to fix them both in servicing.

Disabling pruning can help with diagnosing the problem but I don't recommend doing so in production. Doing so you end up shipping the package copy of Drawing.Common rather than the framework copy. We'd like folks to use the latest framework copy and not be responsible for updating a package.

dotnet/sdk#51173 (comment) works-around the compilation issue. dotnet/windowsdesktop#5405 (comment) works-around the load issue for self contained applications.

OK, I'm still using .NET 9 in my project for now, and I'll switch to .NET 10 once the issue is fixed in the publish.