You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting with SkiaSharp 3.x the libSkiaSharp.dll is no longer copied into the output directory. This happens for older .NET Framework projects that still use packages.config instead of the new PackageReference inside the csproj file.
This affects both .NET Framework and Mono projects:
Description
Starting with SkiaSharp 3.x the
libSkiaSharp.dll
is no longer copied into the output directory. This happens for older .NET Framework projects that still usepackages.config
instead of the newPackageReference
inside the csproj file.This affects both .NET Framework and Mono projects:
Code
Example
packages.config
file:Expected Behavior
The build directory should contain
x86
,x64
,arm64
containing thelibSkiaSharp.dll
/libSkiaSharp.so
/libSkiaSharp.dylib
.Actual Behavior
Nothing is copied into the output directory. Unless the project was migrated from
packages.config
toPackageReference
.Version of SkiaSharp
3.116.0 (Current)
Last Known Good Version of SkiaSharp
2.88.9 (Previous)
IDE / Editor
Visual Studio (Windows)
Platform / Operating System
Windows
Platform / Operating System Version
No response
Devices
No response
Relevant Screenshots
No response
Relevant Log Output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: