Hi Graham In order to keep Windows UAC happy you need to code sign your app (and installer if you use one) with a certificate authorised by a third party (such as Verisign)
I found getting set up to do this a pain in the **** because to get your third party certificate you have to prove your identity to them - not so bad if you are an individual but if you want to have the name of your business appear as the 'publisher' then it can take a bit more hassle. Then when you get your certificate (and have paid your money), you get to download it - but it will only work on the machine you ordered the certificate from so be careful! Once it's installed properly I use a Microsoft tool such as signtool.exe to sign each .exe or .dll file as needed Basically it's a lot of hassle (but necessary if you want your software to appear professional on Windows) and people do come unstuck (for example the only-working-on-one-machine issue and there is no way to reset the certificate's password) so research carefully before you start and don't expect to get it all done and dusted without effort. Good luck! Dave ----- "Some are born coders, some achieve coding, and some have coding thrust upon them." - William Shakespeare & Hugh Senior -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/OT-Legitimising-a-developer-as-a-publisher-in-Windows-7-tp4685315p4685316.html Sent from the Revolution - User mailing list archive at Nabble.com. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
