Conform to User Account Control on Windows

[x87]

Windows prevents or alters some operations:
https://en.wikipedia.org/wiki/User_Account_Control#Tasks_that_trigger_a_UAC_prompt

If Sanny Builder runs with non-elevated rights (user) the following would not work:

• file association 3.5.0 Release Plan #47
• writing settings.ini* (when it's installed In Program Files)
• updating opcodes.txt* Explore Command Line Enhancements #14
• saving new templates* User templates should be stored in a separate file and kept between updates #154
• any decompiler and compiler output run against files located in Program Files*

* Windows generates those files in "C:\Users\username\AppData\Local\VirtualStore\Program Files\Sanny Builder 3" thanks to File and Registry Virtualization

This can be bypassed if run sanny.exe as administrator.

[x87]

adding a manifest file as suggested prompts an elevation request on each start, that's not very convenient.

[CookiePLMonster]

• Windows generates those files in "C:\Users\username\AppData\Local\VirtualStore\Program Files\Sanny Builder 3" thanks to File and Registry Virtualization

The fact registry virtualization is still used with Sanny is a bad sign, as it's supposed to be used only for legacy, UAC unaware applications. Sanny shouldn't be UAC unaware.

[x87]

@CookiePLMonster Sanny is legacy 🤷‍♂️

So far I think I managed to avoid the need for admin rights for the file association. Previously it used HKEY_CLASSES_ROOT which is not a recommended way nowadays. Now Sanny uses HKEY_CURRENT_USER\Software\Classes

I'm not sure what to do with the File Virtualization when Sanny is installed in Program Files. While I can move settings.ini to AppData, self-updating the rest of files in Sanny's data folder would seem impossible without admin rights.

[OrionSR]

My experience is that file associations don't work when Sanny is already running in administrative mode. To be more specific, if I double-click on a file with the File Explorer and Sanny is running then it seems to get stuck instead of prompting for admin confirmation. For this reason I prefer to run Sanny with non-elevated status.

To overcome many of the other limitations mentioned, I don't install Sanny or the games in Program Files and run Sanny without elevation. Most functions seem to work as expected except the Coords Manager can't access game memory, and Run Game (F8) doesn't work.

I've been considering installing SB-3.5 using the default install options on my Win10 machine to get a better idea of the issues most users are struggling with. But then again, I would expect Win10 to fight with me as I try to update my edit modes. Not just with Sanny but any other tool I use to organize the files in Sanny's directories.