[OT?] Legitimising a developer as a 'publisher' in Windows 7

[J. Landman Gay]

My client is using ksoftware certs. Applying the cert is done after LC 
is finished creating the app. Once you've been through the rigmarole of 
obtaining the cert (pain in the patoot) you just use ksoftware's utility 
to select your app and click a button that embeds the certificate. It's 
a one-click deal.

You can use the cert on as many apps as you want, and you should, 
because it identifies the app as coming from you as a verified 
developer. When it expires you need to purchase a new one, but if your 
credentials haven't changed then at least you don't need to go through 
the whole verification process again.

The price goes down a little bit if you buy a certificate that's good 
for several years rather than renewing annually.


On 11/3/2014, 12:23 PM, Bob Sneidar wrote:
> Interesting. What do you do? Run an application that applies the code
> signing certificate to the application? Or is there something in
> Livecode we would need to do?
>
> Also, is the cert on a per app basis, or is it $95/yr for ALL apps
> you develop?
>
> Bob S
>
>
>> On Nov 2, 2014, at 04:09 , Guglielmo Braguglia
>> <guglielmo at braguglia.ch> wrote:
>>
>> Hi, have a look here : http://codesigning.ksoftware.net ... is
>> quite cheap (... probably one of the cheapest) and work very well
>> (I use it for several years) ;)



-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com