Open TommiPrami opened 7 years ago
I know, but i did not add a manifest on purpose. Since i haven't bought a proper certificate yet. I am not a fan of unsigned administrative manifests.
However, it should work, if you install to a location the current user has write access to. The default setting of ProgramFiles(x86) is the culprit here.
Oh yes... That is an real problem, the certificate.
Can we detect that program is not running on Elevated or similar rights. And program could tell user, that try running me as Admin. That would be more than enough for me.
As a kludge testing read/write etc access to installation folder would do. But not very elegant, there must be better way.
Yes, good idea. it should at least check for read/write access for the given folder. PS: Even checking for administrative rights is not enough. What if the folder is owned by SYSTEM? That would still fail. PSS: I'll look into what i can do. Maybe Displaying 2 messages. One somewhere in the UI that it has NO administrative privileges, and one which clarifies that it can not read/write to the specified folder.
At least in my environment it does not work if I do not run installer as Administrator.
Would make things easier if the installer would ask at startup that it needs to be elevated.