We have an installer for our application, which must be downloaded and run with administrator privileges, like many other installers. However, the installer is not named "setup.exe", so Windows does not automatically detect it as requiring elevation to run.
Changing the name of the installer to make things elevated sounds pretty dirty, honestly. This article talks a lot about UAC and promotion, and it says that you can use the manifest to require authorization for something.
So, we just wanted to create a manifest for our installer. However, how do we guarantee that the manifest is present? If the user simply downloads our_application_v13.exe, how do we guarantee that he will also receive the manifest? In this case, the AFAIK manifest must be a file named "our_application_v13.exe.manifest".
Since they just download the file from our website, how can we make sure they get the manifest too? Can we somehow create it in an executable file or otherwise specify the executable file as requiring a raise? We use an installation tool from hundreds of years ago that we cannot change, so it does not have any features related to this.
Thanks!
Colen