Vinny
2nd May 2012, 14:48
Hi all,
I'm currently trying to make a fully operationnal setup program in order to deploy my application on Vista and Seven systems (both 32 and 64bit, but the executable is the same).
My issue concerns the setup program itself, which is not detected by UAC as a setup program (It is actually executed after an Winrar-created SFX extraction, I don't know if thats relevent). So the UAC doesn't ask the user for administrator rights, and the setup runs in user mode. As the default path is in program files, the setup doesn't have rights to write its files. Strange thing though, QFile::copy() doesn't produce any error.
What I would like is the setup to ask for administrator rights elevation as soon as it starts. I tried to embed a Installer.exe.manifest file in the executable resources and adding embed_manifest_exe option in the *.pro file.
What is the proper way to perform this ?
Furthermore, when running the application, some files inside the installation directory may be written. Again it is mandatory to run explicitely the application as administrator to avoid unpleasant behaviours, but this time I guess it is more of an application design error.
I'm currently trying to make a fully operationnal setup program in order to deploy my application on Vista and Seven systems (both 32 and 64bit, but the executable is the same).
My issue concerns the setup program itself, which is not detected by UAC as a setup program (It is actually executed after an Winrar-created SFX extraction, I don't know if thats relevent). So the UAC doesn't ask the user for administrator rights, and the setup runs in user mode. As the default path is in program files, the setup doesn't have rights to write its files. Strange thing though, QFile::copy() doesn't produce any error.
What I would like is the setup to ask for administrator rights elevation as soon as it starts. I tried to embed a Installer.exe.manifest file in the executable resources and adding embed_manifest_exe option in the *.pro file.
What is the proper way to perform this ?
Furthermore, when running the application, some files inside the installation directory may be written. Again it is mandatory to run explicitely the application as administrator to avoid unpleasant behaviours, but this time I guess it is more of an application design error.