-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Description
Description
With Visual Studio 2022 I had no problems at all — I could load Icon, Bitmap, and the rest without any issues, just by having the System.Drawing.Common NuGet package.
Yesterday I upgraded to Visual Studio 2026… and what a mess. Now it warns me that the library won’t be removed, but that I should consider removing it…
So, if I remove it and make some changes, debugging works fine; but the moment I make a PORTABLE (self-contained) publish, that’s when the party starts. Since it doesn’t copy the System.Drawing.Common.dll library into the final output assemblies, the application blows up everywhere. It can’t find the library — which makes sense, because it doesn’t exist since I was “forced” to remove it — but it’s obvious that some internal .NET 10 crap still needs it.
In short, if I include it as a NuGet package, when publishing or building, it NEVER copies it to the output folder, so I can’t create a portable application.
What a disaster of an update from Microsoft… it’s always the same, you have to wait at least 4 or 5 months until the new VS becomes stable… pathetic.
Reproduction Steps
Add the System.Drawing.Common package, publish the project as portable (self-contained), and voilà — there’s no System.Drawing.Common.dll anywhere.
Expected behavior
If the System.Drawing.Common package is added… when publishing as self-contained, it should include the library!
Actual behavior
Add the System.Drawing.Common package, publish the project as portable (self-contained), and voilà — there’s no System.Drawing.Common.dll anywhere.
Regression?
No response
Known Workarounds
No response
Impact
Critical
Configuration
No response
Other information
No response