-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add RequestUninstallerExecutionLevel #18
base: master
Are you sure you want to change the base?
Add RequestUninstallerExecutionLevel #18
Conversation
This does not actually work. |
Maybe now? Added the enum value |
Have you actually verified that this works? I would expect changes to build.cpp. |
Frankly, no, haven't had the time to set up a dev environment. But it looks simple enough, and I'll happily test the resulting pre-release binaries.
Why? |
Because the uninstaller is generated from the installer. Your code changes probably have zero effect. |
There is only one Line 1554 in de09827
|
So I read a bit more of the code. As far as I understand, the uninstaller is created by the installer as a delta of its own, which is something I didn't realize before. I thought of a solution, and I think what can be done is changing the code here: I might get back to it later. Now, I have two options that I see: use the old hack, or change the uninstaller code to elevate at startup, without a manifest. The "elevate at startup" option has pros: less disk space in the installer, less hacks in the code, and cons: the process is being launched twice, Windows doesn't show shield icon. |
I tried to implement
RequestUninstallerExecutionLevel
, see https://sourceforge.net/p/nsis/feature-requests/560/It's a small change, but helps me get rid of a large hack. Please accept this change to help me avoid maintaining a fork, and to help others who need this small feature.