Good info, thanks for that. My client didn't want an installer (they
used to use one but for this app they wanted a plain zip file.) It's
useful to know that the dll isn't signed though, for future reference.
We did ask one affected person to move the app folder to their Documents
folder and all was well. This person was using a university-issued
computer that likely enforced some stricter permissions. Putting the app
on the Desktop failed, putting it in Documents was okay.
Don't ask me, I just work here.
On 1/15/2016 8:21 PM, tbodine wrote:
Followup on the code signing hunch:
We know in the Apple world a lack of code signing can get an app banished by
Apple's Gatekeeper. So perhaps a Windows machine with high security
requirements also blocks exes or dlls that are not signed.
It looks to me like RunRev does not code sign the dlls used for Windows
standalone builds. In a spot check of the externals in my LC 7.1.1
commercial installation on Windows 7, I see several external dlls there are
not code signed by RunRev. (I did not check them all.) Dlls in my
standalones are also not signed until I do that myself.
Innosetup has the capability of calling your code signing tool and signing
the dlls and executable as part of its installer compiling process. Using
that, my dlls get code signed painlessly.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.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
