Repository navigation
Replace the personal-install launcher with a native C executable - #86
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Personal installations currently carry a separate .NET runtime just to start a scheduled task. Replace that managed launcher with a small C executable (about 62 KiB for production), built with the existing pinned Zig compiler. It starts only the current user's MegaProxy task and retains the PROD/DEV names, icons and version resources.
Remove obsolete launcher files from the previous installation inventory during upgrades, including rollback backups. Keep the main application and its runtime in the protected installation directory. Add native PE checks and installer checks for obsolete-file selection and absence of launcher DLLs.
Validation: PROD and DEV native builds passed; setup checks built without warnings and passed; 13 Python packaging, runtime-payload and license tests passed. Full installation/upgrade and real scheduled-task launch remain for CI smoke tests.