The most recent, and potentially unstable build, will be in the main
branch. Releases are branched/tagged with semantic version numbers (ie. v2.3.4
). WIP Features and will usually be housed in temporary branches – these branches are often deleted when no longer needed.
I develop my documentation in Obsidian. In this repo, he obsidian
branch is a WIP documentation branch that contains automatic checkins from Obsidian. These are merged (and squashed) back into main periodically.
I’ve turned this into a Microsoft Visual Studio Solution to organize the dependencies between the resource project (skvfximageres
), the batch files (UE_QuickLaunch
) and the installer (UE_QuickLaunch_installer
) projects. I use Microsoft Visual Studio Community 2022
The installer is built using WiX v4, and uses the HeatWave extension:
If you load the solution and the installer project comes up as “incompatible” (you’ll get an error on load), just enable the extension, restart, and then right click on the UE_QuickLaunch_installer project, and select “reload project” (or something similar to that).
If you’re interested in learning how to make an MSI installer using something like HeatWave, I found the Wix v4 documentation pretty impenetrable, but ChatGPT did a pretty good job at getting me started with the xml syntax.
The installer, UE_QuickLaunch_installer.msi
, runs unassisted and builds into the UE_QuickLaunchInstaller/bin folder and installs to ProgramFiles/SKVFX UE_QuickLaunch
. It can be uninstalled/modified, in Window’s Settings > Apps > Installed apps.
wix convert
to get a better idea how to format the v4 version. This is helping, but what a PITA. Document your fucking code.msiexec /i UE_QuickLaunch_installer.msi /L*v ".\InstallLog.txt"