-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to run published Avalonia app #1665
Comments
has this lib in app folder? |
I don't see libSkiaSharp dll in any of the published files, even in publish folder. |
Any news? |
In a very simple project (the "Hello World" button from the Quick Start but set for .NET Core only) my top-level exception is the one that reports unable to load libSkiaSharp.dll. I get this publishing from VS2017 targeting win-x64 portable + Framework-dependent, so I tried publishing as self-contained but it still throws the same error. SkiaSharp.dll is in the stand-alone publish folder, but libSkiaSharp.dll is not. I thought this might be one of those NuGet transient-dependency problems, but even if I added a reference to the SkiaSharp package (version 1.57.1, same as Avalonia uses right now) and re-published as self-contained, the DLL still isn't published. I'm wondering if it's a mismatch with SkiaSharp's NuGet package runtime list. VS is using |
Are you using the nightly builds? |
I replaced win-x64 with win10-x64 and it works now |
This is probably a documentation issue, ultimately -- both here and for SkiaSharp (I'll open an issue over there and cross-reference this). By default, VS Publish only lists the fallback runtime IDs which is why I only saw the less-specific <RuntimeIdentifiers>win10-x64;osx;linux-x64</RuntimeIdentifiers> After this change, both the However, publishing to the I'm new to Avalonia (and I understand Avalonia is still very much a work-in-progress), should I expect OSX to build and publish yet? |
@byme8 you should use win7-x64, win-x64 is actually for targeting win-rt which isn't officially supported. |
@danwalmsley Just for the record, that isn't what WinRT doesn't have an RID -- you can't use it as a publish target (which makes sense, as it has been discontinued). CoreRT is the new runtime targeting AOT (ahead-of-time compile) scenarios -- basically taking over from WinRT as Microsoft's end-game of getting rid of the Win32 API once and for all. The first section of that article defines the full RID format as You could confirm this with a self-contained publish targeting one of the version-specific Linux RIDs. You should still get the Linux version of libSkiaSharp because the |
build environment: win10 v1809 x64. |
Closing this because the original repro is no longer available. |
A repro of the issue can be found here
I have a window with an Image control that renders a PNG from Assets folder. When I run the application from visual studio the Image renders fine on the window, but when I publish the dotnet app in Windows OS and run the exe, the application fails to start. I found the issue after doing dotnet Applicationname.dll and got the following exception:
The text was updated successfully, but these errors were encountered: