Another thing to watch out for is timestamping. If you apply a timestamp as you code sign a file then when your code signing certificate expires the certificate on your file continues to be recognised by UAC - if you don't apply a timestamp then when your certificate expires the certificate on your file stops being recognised.
So for anything you think might continue being used after the life of your certificate consider applying a timestamp Dave PS: I guess if you renew your code signing certificate before it expires that the certificate on the file will continue to be recognised by verisign (or whoever) and thus continue to be recognised as valid by Microsoft UAC ----- "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-tp4685315p4685374.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
