.net - How to sign my VB.NET application? -


i'd avoid scary messages when users install application:

screenshot unknown publisher

i understand have buy certification or that. can tell me should buy , should after? i'd sign exe application automatically. furthermore, use innosetup , i'd add signature automatically when creating new package (exe file)

if want "known publisher" need certificate authority verisign, etc. it's not cheap (verisign charges ~$400/yr).

https://www.symantec.com/verisign/code-signing/microsoft-authenticode/buy

see :

http://msdn.microsoft.com/en-us/library/ms247066

https://stackoverflow.com/a/1191152/327083

basically there 2 things can - strong name signing , authenticode signing.

strong name signing alone not identify publisher of assembly associate assembly trusted key , can detect assemblies have been tampered with. have distribute own key/certificate users , have them install them. there no third-party system in place handle this.

authenticode (ie: verisign, etc) costs money third party certification allows entire process nicely shrink-wrapped , identifies known publisher.

still, users still see dialog box default uac settings verisign certificate (at least first time) - identify came (known publisher, name, etc). would, however, option "always trust" publisher (which not 'unknown publisher').


Comments

Popular posts from this blog

c# - SVN Error : "svnadmin: E205000: Too many arguments" -

c# - Copy ObservableCollection to another ObservableCollection -

All overlapping substrings matching a java regex -