Open 64bit-awesome opened 2 years ago
Hi, thank you and appreciate the help. Unfortunately there is a few edge cases like in the store build the plugins are published with .net core self-contained and others just the build is used (installer.) There is also difference in structure between the store and installer (UI\Build\Lively.exe for store.)
I wish to make the store and installer into a single project in the future, then we can take a look at this issue.
Outlining the current build process
Installer (x86):
Lively/Plugins/Cef
folder.Lively/Plugins/Mpv
folder.Lively/Plugins/UI/
Frame-work dependent
setting (visual studio will copy bundle and plugins to output.)Microsoft store:
Frame-work included
setting.Lively.UI.WinUI\Build
folder.Lively.UI.WinUI
into msix."C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86\MakeAppx.exe" bundle /d "C:\src" /p C:\dest\out.msixbundle
Is your feature request related to a problem? Please describe. From my understanding, building lively on Visual Studio requires manually creating the plugins folder in the core project and copying over the build output from the plugins (UI, Watchdog, PlayerWebView2, PlayerWmf) every time they are modified. This must be tedious to do for every build.
Describe the solution you'd like There is an easier way to do this!
Visual Studio can take care of creating the 'Plugins' folder if it does not exist and copying the build output to the correct folder in the plugins directory automatically when re-building the solution. All that is needed is to configure the csproject files and the sln file and the UI, Watchdog, PlayerWebView2, and PlayerWmf plugins are automatically copied to the Lively plugin directory after they are built. I think this makes the process easier.
I created a pull request and linked it if you would like to incorporate my changes.
Note lively-cef and mpv plugins will still need to be manually copied over since they are not in the same visual studio solution.