Single-file publishing now supports DB mods and update_loader.dat. This fixes the crash when attempting to use DB mods and the failure to re-launch after updating AuroraLoader that would occur when using a single-file release of 0.22.3ish.
For convenience, the following files are now copied to the output directory when using single file publish:
aurora_versions.ini`
mirrors.ini
mod.ini
update_loader.ini
The above involved changing several references from AppDomain.CurrentDomain.BaseDirectory (which refers to a temp directory when running a .NET Core 3 single-file .exe) to AuroraLoaderExecutableDirectory (which always refers to the directory the actual .exe is in).
Finally, I ran Visual Studio's built in 'clean up imports' tool, and apparently the packages we publish are MUCH smaller now - 1.2mb compared to over 32mb!
Note that I'm publishing with the following options:
Single-file publishing now supports DB mods and
update_loader.dat. This fixes the crash when attempting to use DB mods and the failure to re-launch after updating AuroraLoader that would occur when using a single-file release of 0.22.3ish.For convenience, the following files are now copied to the output directory when using single file publish:
mirrors.inimod.iniupdate_loader.iniThe above involved changing several references from
AppDomain.CurrentDomain.BaseDirectory(which refers to a temp directory when running a .NET Core 3 single-file .exe) toAuroraLoaderExecutableDirectory(which always refers to the directory the actual .exe is in).Finally, I ran Visual Studio's built in 'clean up imports' tool, and apparently the packages we publish are MUCH smaller now - 1.2mb compared to over 32mb!
Note that I'm publishing with the following options:
That results in the following zip: AuroraLoader.0.22.4.zip