Replies: 3 comments
-
For installers the recommended approach is to use platform-specific options:
|
Beta Was this translation helpful? Give feedback.
-
Avalonia does not forces you to use some specific way to install the application. Neither it implements it without you. It's GUI framework, not packaging system. Search for dotnet packaging and publishing. |
Beta Was this translation helpful? Give feedback.
-
Thanks for your suggestions, i'll explore them. |
Beta Was this translation helpful? Give feedback.
-
Hi all.
So i came across the situation where i want the end user to install my software (downloaded as single executable).
Because i couldn't find a way to use "installer project" with Avalonia i was trying to think a way to do so.
my thought was:
Before doing so i had a reject of my own - there will be a lot of duplicate files (.net core and Avalonia libraries, once in the software and another in the installer) in this mongrel project which will result a bloated executable file.
Of course there is a way to publish both as platform dependant (to exclude .net core libraries completely) but i am trying to avoid "must haves" installations.
As for now i am bushwhacking to find a way exracting core libraries from the installer project into the "installation path", that way i will be able to exclude those from the "software project" - no much success so far.
Has anyway ever faced this situation or have an idea how to accomplish a reasonable solution?
Beta Was this translation helpful? Give feedback.
All reactions