All projects (rpkg dll, cli, and gui) have been merged into a single solution and their configurations have been updated in order to be able to properly compile in both Release and Debug mode and for the GUI to use the build version of the DLL without requiring manually copying it.
This includes a few other notable changes:
The GUI has also been updated to use the project-based NuGet package definition schema instead of the old packages.config method.
The RPKG dll (rpkg.dll) is only bundled into the GUI executable in Release builds. Debug builds do not bundle it to allow for faster iteration and easier debugging.
The ResourceLib binaries (ResourceLib_HM2.dll and ResourceLib_HM3.dll) are no longer bundled into the GUI executable (since its a GPL violation), and are instead expected to be placed alongside it in a folder. If you get a module not found error while trying to run it under VS, you just need to download ResourceLib and put it in the _build/Debug or _build/Release folder.
All projects (rpkg dll, cli, and gui) have been merged into a single solution and their configurations have been updated in order to be able to properly compile in both
ReleaseandDebugmode and for the GUI to use the build version of the DLL without requiring manually copying it.This includes a few other notable changes:
packages.configmethod.rpkg.dll) is only bundled into the GUI executable inReleasebuilds. Debug builds do not bundle it to allow for faster iteration and easier debugging.ResourceLibbinaries (ResourceLib_HM2.dllandResourceLib_HM3.dll) are no longer bundled into the GUI executable (since its a GPL violation), and are instead expected to be placed alongside it in a folder. If you get amodule not founderror while trying to run it under VS, you just need to download ResourceLib and put it in the_build/Debugor_build/Releasefolder.