[OT, maybe] - configuring a Windows Installer for a Standalone

Bob Sneidar bobsneidar at iotecdigital.com
Thu Apr 5 10:46:08 EDT 2018


Just poking around, a manifest is like a config file for the app. As I mentioned, your installer maker solution may have a way to configure one. If not, apparently there are solutions that allow you to post process your executable to include one. 

Also worth considering, in the Windows tab of the Standalone Application Settings, at the bottom of the window is a popup menu for UAC settings. Unless your app will require Administrative Access to the file system, I would set this to Same as Invoker. Apparently this wil create some kind of manifest. Also, the app will run with the same permissions as the caller. This should prevent Windows from thinking the app must be run as an administrator. 

Bob S


> On Apr 5, 2018, at 06:58 , Graham Samuel via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> Hmm, thanks for the discussion. I see that it is not a straightforward issue, and I am probably forced to get my hands dirty in the world of Windows. I am aching for a very simple set of step-by-step instructions, but of course that is not the job of anyone on this list! BTW, I am also asking in the Inno Setup forum, and have had some replies, but despite my references to LiveCode, it appears that nobody there can believe I’m not using Visual Basic or C++. There is dark talk of manifests, about which I know nothing, but maybe I can piece together an idiot’s solution.



More information about the Use-livecode mailing list